| commit | a52b2f87f76cfb381613656461a52e0b222bf976 | |
| author | Stefan Agner <stefan@agner.ch> | |
| Thu, 11 Jan 2018 13:47:40 +0000 (11 14:47 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Wed, 17 Jan 2018 08:29:31 +0000 (17 09:29 +0100) | ||
| tree | 3b1523e5f0888ae23e72cf67a266b6bc5d759323 | treesnapshot (tar.gz zip) |
| parent | 8b3193a1f8d1b31bffcabc918c9bcfb32ea1572d | commitdiff |
usb: misc: usb3503: make sure reset is low for at least 100us
commit b8626f1dc29d3eee444bfaa92146ec7b291ef41c upstream.
When using a GPIO which is high by default, and initialize the
driver in USB Hub mode, initialization fails with:
[ 111.757794] usb3503 0-0008: SP_ILOCK failed (-5)
The reason seems to be that the chip is not properly reset.
Probe does initialize reset low, however some lines later the
code already set it back high, which is not long enouth.
Make sure reset is asserted for at least 100us by inserting a
delay after initializing the reset pin during probe.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit b8626f1dc29d3eee444bfaa92146ec7b291ef41c upstream.
When using a GPIO which is high by default, and initialize the
driver in USB Hub mode, initialization fails with:
[ 111.757794] usb3503 0-0008: SP_ILOCK failed (-5)
The reason seems to be that the chip is not properly reset.
Probe does initialize reset low, however some lines later the
code already set it back high, which is not long enouth.
Make sure reset is asserted for at least 100us by inserting a
delay after initializing the reset pin during probe.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/usb/misc/usb3503.c | diffblobblamehistory |