linux/drivers/usb
Daniel Mack b3a3dd074f USB: fix gathering of interface associations
TEAC's UD-H01 (and probably other devices) have a gap in the interface
number allocation of their descriptors:

  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          220
    bNumInterfaces          3
    [...]
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      [...]
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         2
      bInterfaceCount         2
      bFunctionClass          1 Audio
      bFunctionSubClass       0
      bFunctionProtocol      32
      iFunction               4
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      [...]

Once a configuration is selected, usb_set_configuration() walks the
known interfaces of a given configuration and calls find_iad() on
each of them to set the interface association pointer the interface
is included in.

The problem here is that the loop variable is taken for the interface
number in the comparison logic that gathers the association. Which is
fine as long as the descriptors are sane.

In the case above, however, the logic gets out of sync and the
interface association fields of all interfaces beyond the interface
number gap are wrong.

Fix this by passing the interface's bInterfaceNumber to find_iad()
instead.

Signed-off-by: Daniel Mack <zonque@gmail.com>
Reported-by: bEN <ml_all@circa.be>
Reported-by: Ivan Perrone <ivanperrone@hotmail.com>
Tested-by: ivan perrone <ivanperrone@hotmail.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2012-06-14 17:13:34 -07:00
..
atm USB: xusbatm.c: remove dbg() usage 2012-05-01 21:33:30 -07:00
c67x00
chipidea usb: chipidea: remove zero check of hw_ep_max 2012-05-15 08:43:40 -07:00
class usb: cdc-acm: fix devices not unthrottled on open 2012-06-14 17:13:33 -07:00
core USB: fix gathering of interface associations 2012-06-14 17:13:34 -07:00
dwc3 usb: dwc3: Fix the dwc3 dependency 2012-05-11 15:17:31 -07:00
early
gadget usb: gadget: regression fix - usage of usb_ep 2012-06-04 18:24:49 +03:00
host usb: ehci-sh: fix illegal phy_init() running when platform_data is NULL 2012-06-14 17:13:34 -07:00
image USB: mdc800.c: remove dbg() usage 2012-05-01 21:33:50 -07:00
misc USB: yurex.c: remove dbg() usage 2012-05-01 21:34:11 -07:00
mon
musb usb: musb_gadget: fix crash caused by dangling pointer 2012-06-04 18:30:20 +03:00
otg USB: gpio_vbus: wakeup support on GPIO VBUS interrupts 2012-05-17 11:20:34 -07:00
phy USB: Add driver for NXP ISP1301 USB transceiver 2012-05-01 13:33:02 -04:00
renesas_usbhs usb: renesas_usbhs: gadget: add support for set_selfpowered 2012-05-04 15:53:05 +03:00
serial usb: use usb_serial_put in usb_serial_probe errors 2012-06-13 17:26:11 -07:00
storage usb-storage: Add 090c:1000 to unusal-devs 2012-06-13 16:29:58 -07:00
wusbcore
Kconfig usb: move ci13xxx and related code to drivers/usb/chipidea 2012-05-11 16:45:30 -07:00
Makefile usb: move ci13xxx and related code to drivers/usb/chipidea 2012-05-11 16:45:30 -07:00
README
usb-common.c
usb-skeleton.c USB: usb-skeleton.c: remove err() usage 2012-04-27 11:24:45 -07:00

To understand all the Linux-USB framework, you'll use these resources:

    * This source code.  This is necessarily an evolving work, and
      includes kerneldoc that should help you get a current overview.
      ("make pdfdocs", and then look at "usb.pdf" for host side and
      "gadget.pdf" for peripheral side.)  Also, Documentation/usb has
      more information.

    * The USB 2.0 specification (from www.usb.org), with supplements
      such as those for USB OTG and the various device classes.
      The USB specification has a good overview chapter, and USB
      peripherals conform to the widely known "Chapter 9".

    * Chip specifications for USB controllers.  Examples include
      host controllers (on PCs, servers, and more); peripheral
      controllers (in devices with Linux firmware, like printers or
      cell phones); and hard-wired peripherals like Ethernet adapters.

    * Specifications for other protocols implemented by USB peripheral
      functions.  Some are vendor-specific; others are vendor-neutral
      but just standardized outside of the www.usb.org team.

Here is a list of what each subdirectory here is, and what is contained in
them.

core/		- This is for the core USB host code, including the
		  usbfs files and the hub class driver ("khubd").

host/		- This is for USB host controller drivers.  This
		  includes UHCI, OHCI, EHCI, and others that might
		  be used with more specialized "embedded" systems.

gadget/		- This is for USB peripheral controller drivers and
		  the various gadget drivers which talk to them.


Individual USB driver directories.  A new driver should be added to the
first subdirectory in the list below that it fits into.

image/		- This is for still image drivers, like scanners or
		  digital cameras.
../input/	- This is for any driver that uses the input subsystem,
		  like keyboard, mice, touchscreens, tablets, etc.
../media/	- This is for multimedia drivers, like video cameras,
		  radios, and any other drivers that talk to the v4l
		  subsystem.
../net/		- This is for network drivers.
serial/		- This is for USB to serial drivers.
storage/	- This is for USB mass-storage drivers.
class/		- This is for all USB device drivers that do not fit
		  into any of the above categories, and work for a range
		  of USB Class specified devices. 
misc/		- This is for all USB device drivers that do not fit
		  into any of the above categories.