On Monday, August 24, 2015 at 08:57:02 PM, Stephen Warren wrote:
> On 08/23/2015 09:47 PM, Marek Vasut wrote:
> > On Friday, August 21, 2015 at 11:58:55 PM, Stephen Warren wrote:
> >> On 08/20/2015 11:34 PM, Marek Vasut wrote:
> >>> On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
>
On 08/23/2015 09:47 PM, Marek Vasut wrote:
On Friday, August 21, 2015 at 11:58:55 PM, Stephen Warren wrote:
On 08/20/2015 11:34 PM, Marek Vasut wrote:
On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
From: Stephen Warren
When an EHCI device is registered in device mode, the H
On Friday, August 21, 2015 at 11:58:55 PM, Stephen Warren wrote:
> On 08/20/2015 11:34 PM, Marek Vasut wrote:
> > On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
> >> From: Stephen Warren
> >>
> >> When an EHCI device is registered in device mode, the HW isn't actually
> >> initi
On 08/20/2015 11:34 PM, Marek Vasut wrote:
On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
From: Stephen Warren
When an EHCI device is registered in device mode, the HW isn't actually
initialized at all, and hence isn't left in a running state. Consequently,
when the device is
On Friday, August 21, 2015 at 01:38:05 AM, Stephen Warren wrote:
> From: Stephen Warren
>
> When an EHCI device is registered in device mode, the HW isn't actually
> initialized at all, and hence isn't left in a running state. Consequently,
> when the device is deregistered, ehci_shutdown() will
From: Stephen Warren
When an EHCI device is registered in device mode, the HW isn't actually
initialized at all, and hence isn't left in a running state. Consequently,
when the device is deregistered, ehci_shutdown() will fail, since the HW
bits it expects to see set in response to its shutdown r
6 matches
Mail list logo