Re: [PATCH v7 14/16] usb: resume (wakeup) child device when port is powered on

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 29 Apr 2014, Dan Williams wrote:

> > What happens if a thread tries to resume or suspend a port while the
> > hub is being reset?  With nothing to prevent it, the request sent to
> > the hub will fail and the port may end up in a runtime PM error state.
> >
> 
> I'm expected to be protected by:
> 
>         /* Prevent autosuspend during the reset */
>         usb_autoresume_device(udev);
> 
> ...in usb_reset_device() and usb_reset_and_verify_device()'s
> requirement that the device in question not be suspended.  The hub
> should pin it's parent port active during the reset.

My question wasn't clear enough.  What happens if, while hub H is being
reset, a thread tries to resume a port on hub H (not on H's parent)?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux