diff options
| author | Ben McCauley <ben.mccauley@garmin.com> | 2015-11-16 10:47:24 -0600 |
|---|---|---|
| committer | Felipe Balbi <balbi@ti.com> | 2015-11-17 11:35:48 -0600 |
| commit | b9e51b2b1fda19143f48d182ed7a2943f21e1ae4 (patch) | |
| tree | 33239cdda81290cbf5c12c3c262209ea52b82ce3 /drivers/usb/phy | |
| parent | 68fe05e2a45181ce02ab2698930b37f20487bd24 (diff) | |
| download | linux-stable-b9e51b2b1fda19143f48d182ed7a2943f21e1ae4.tar.gz linux-stable-b9e51b2b1fda19143f48d182ed7a2943f21e1ae4.tar.bz2 linux-stable-b9e51b2b1fda19143f48d182ed7a2943f21e1ae4.zip | |
usb: dwc3: gadget: let us set lower max_speed
In some SoCs, dwc3 is implemented as a USB2.0 only
core, meaning that it can't ever achieve SuperSpeed.
Currect driver always sets gadget.max_speed to
USB_SPEED_SUPER unconditionally. This can causes
issues to some Host stacks where the host will issue
a GetBOS() request and we will reply with a BOS
containing Superspeed Capability Descriptor.
At least Windows seems to be upset by this fact and
prints a warning that we should connect $this device
to another port.
[ balbi@ti.com : rewrote entire commit, including
source code comment to make a lot clearer what the
problem is ]
Cc: <stable@vger.kernel.org>
Signed-off-by: Ben McCauley <ben.mccauley@garmin.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
Diffstat (limited to 'drivers/usb/phy')
0 files changed, 0 insertions, 0 deletions