From: William wu
On some platforms(e.g. rk3399 board), we can call hcd_add/remove
consecutively without calling usb_put_hcd/usb_create_hcd in between,
so hcd->flags can be stale.
If the HC dies due to whatever reason then without this patch we get
the below error on next hcd_add.
[173.296154] x
William,
On 12/01/17 14:03, William Wu wrote:
> From: William wu
>
> On some platforms(e.g. rk3399 board), we can call hcd_add/remove
> consecutively without calling usb_put_hcd/usb_create_hcd in between,
> so hcd->flags can be stale.
>
> If the HC dies due to whatever reason then without this
On Thu, 12 Jan 2017, Roger Quadros wrote:
> William,
>
> On 12/01/17 14:03, William Wu wrote:
> > From: William wu
> >
> > On some platforms(e.g. rk3399 board), we can call hcd_add/remove
> > consecutively without calling usb_put_hcd/usb_create_hcd in between,
> > so hcd->flags can be stale.
>
On 12/01/17 17:33, Alan Stern wrote:
> On Thu, 12 Jan 2017, Roger Quadros wrote:
>
>> William,
>>
>> On 12/01/17 14:03, William Wu wrote:
>>> From: William wu
>>>
>>> On some platforms(e.g. rk3399 board), we can call hcd_add/remove
>>> consecutively without calling usb_put_hcd/usb_create_hcd in b
Hi Roger,
在 2017年01月12日 23:38, Roger Quadros 写道:
On 12/01/17 17:33, Alan Stern wrote:
On Thu, 12 Jan 2017, Roger Quadros wrote:
William,
On 12/01/17 14:03, William Wu wrote:
From: William wu
On some platforms(e.g. rk3399 board), we can call hcd_add/remove
consecutively without calling usb
From: William wu
On some platforms(e.g. rk3399 board), we can call hcd_add/remove
consecutively without calling usb_put_hcd/usb_create_hcd in between,
so hcd->flags can be stale.
If the HC dies due to whatever reason then without this patch we get
the below error on next hcd_add.
[173.296154] x