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
> 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.
>>
>>
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
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
4 matches
Mail list logo