Re: [RFC PATCH] USB: enable "power/wakeup" to control remote wakeup in the runtime suspend

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

 



On Tue, 17 Jul 2012, Lan Tianyu wrote:

> > Why is that?  What happens if you power-off a port where the device has
> > remove wakeup enabled?
> >
> I will not power off a port where the device has remote wakeup enabled.
> Only when disabled, the port will power off.

What about the case where the device is active (not suspended)?  Remote 
wakeup won't be enabled then.  Does that mean you're willing to 
power-down a device when it is active but not when it is suspended (if 
remote wakeup is enabled)?  That doesn't make sense.

> > But in general, if a driver needs wakeup in order to work properly then
> > it _won't_ work when the port is powered off.  So as Oliver says, the
> > user might as well unbind the driver first.
> You mean userspace app unbind the driver?

Yes.

>  But some devices maybe work 
> properly when the port power on again and device is resumed. e.g
> keyboard and mouse.

Userspace can rebind the driver when the port is powered on.

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