diff options
| author | Ben McCauley <ben.mccauley@garmin.com> | 2015-11-16 10:47:24 -0600 |
|---|---|---|
| committer | Luis Henriques <luis.henriques@canonical.com> | 2015-12-14 10:17:09 +0000 |
| commit | 16c99134073c09f6bd40dc8452b137b8068889c8 (patch) | |
| tree | 14630676d76350fed88cd9855fc1b3f98b861023 /include/linux/input.h | |
| parent | e920ac8f55d520200814f9563b2f980d7ebb9848 (diff) | |
usb: dwc3: gadget: let us set lower max_speed
commit b9e51b2b1fda19143f48d182ed7a2943f21e1ae4 upstream.
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 ]
Signed-off-by: Ben McCauley <ben.mccauley@garmin.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
[ luis: backported to 3.16:
- used dev_vdbg() instead of dwc3_trace() ]
Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
Diffstat (limited to 'include/linux/input.h')
0 files changed, 0 insertions, 0 deletions