Re: [U-Boot] [PATCH v3 1/3] usb: hub: identify the hub-device to usb_hub_reset_devices

2017-11-23 Thread Marek Vasut
On 11/22/2017 05:31 PM, Dr. Philipp Tomsich wrote: > >> On 22 Nov 2017, at 17:23, Marek Vasut wrote: >> >> On 11/22/2017 05:15 PM, Philipp Tomsich wrote: >>> When usb_hub_reset_devices is called, it should be passed both an >>> indicator which hub it should operate on and what

Re: [U-Boot] [PATCH v3 1/3] usb: hub: identify the hub-device to usb_hub_reset_devices

2017-11-22 Thread Dr. Philipp Tomsich
> On 22 Nov 2017, at 17:23, Marek Vasut wrote: > > On 11/22/2017 05:15 PM, Philipp Tomsich wrote: >> 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. >> >>

Re: [U-Boot] [PATCH v3 1/3] usb: hub: identify the hub-device to usb_hub_reset_devices

2017-11-22 Thread Marek Vasut
On 11/22/2017 05:15 PM, Philipp Tomsich wrote: > 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

[U-Boot] [PATCH v3 1/3] usb: hub: identify the hub-device to usb_hub_reset_devices

2017-11-22 Thread Philipp Tomsich
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