aboutsummaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-11-22 17:15:17 +0100
committerMarek Vasut <marek.vasut+renesas@gmail.com>2017-11-26 02:22:36 +0100
commit883946e8e7c5dacb5e12f18703e20d49a4886f0e (patch)
treedc763ce48174685b87c9001fff21ff85149f3ba8 /test
parentb3cbcd902db7019410dfe3729a660abcb1f03ffb (diff)
downloadu-boot-883946e8e7c5dacb5e12f18703e20d49a4886f0e.zip
u-boot-883946e8e7c5dacb5e12f18703e20d49a4886f0e.tar.gz
u-boot-883946e8e7c5dacb5e12f18703e20d49a4886f0e.tar.bz2
usb: hub: identify the hub-device to usb_hub_reset_devices
When usb_hub_reset_devices is called, it should be passed both an indicator which hub it should operate on and what port number (local to that hub) should be reset. Previously, the usb_hub.c code did not include such context and always started resets from port number 1, performing multiple reset-requests for the same devices: /* * Reset any devices that may be in a bad state when applying * the power. This is a __weak function. Resetting of the devices * should occur in the board file of the device. */ for (i = 0; i < dev->maxchild; i++) usb_hub_reset_devices(i + 1); This adds an additional 'hub' parameter to usb_hub_reset_devices that provides the context to fully qualify the port-number in. Existing implementations are changed to accept and ignore the new parameter. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions