summaryrefslogtreecommitdiffstats
path: root/drivers/usb/host/ehci-omap.c
diff options
context:
space:
mode:
authorBjørn Mork <bjorn@mork.no>2013-02-13 23:41:34 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-02-13 15:57:53 -0800
commit1f3f687722fd9b29a0c2a85b4844e3b2a3585c63 (patch)
tree0b07be535a59c0a7cf7e3254b02eebdad67ec292 /drivers/usb/host/ehci-omap.c
parentb2ca699076573c94fee9a73cb0d8645383b602a0 (diff)
downloadop-kernel-dev-1f3f687722fd9b29a0c2a85b4844e3b2a3585c63.zip
op-kernel-dev-1f3f687722fd9b29a0c2a85b4844e3b2a3585c63.tar.gz
USB: option: add Huawei "ACM" devices using protocol = vendor
The USB device descriptor of one identity presented by a few Huawei morphing devices have serial functions with class codes 02/02/ff, indicating CDC ACM with a vendor specific protocol. This combination is often used for MSFT RNDIS functions, and the CDC ACM class driver will therefore ignore such functions. The CDC ACM class driver cannot support functions with only 2 endpoints. The underlying serial functions of these modems are also believed to be the same as for alternate device identities already supported by the option driver. Letting the same driver handle these functions independently of the current identity ensures consistent handling and user experience. There is no need to blacklist these devices in the rndis_host driver. Huawei serial functions will either have only 2 endpoints or a CDC ACM functional descriptor with bmCapabilities != 0, making them correctly ignored as "non RNDIS" by that driver. Cc: stable <stable@vger.kernel.org> Signed-off-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/host/ehci-omap.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud