Re: [patch]aggessive autosuspend for HID devices (resent due to corruption)

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

 



On Tue, 2008-10-28 at 01:47 -0700, Oliver Neukum wrote:
> Am Dienstag, 28. Oktober 2008 17:26:02 schrieb Yi Yang:
> > > This uses the USB busy mechanism for aggessive autosuspend of USB
> > > HID devices. It autosuspends all opened devices supporting remote wakeup
> > > after a timeout unless
> > > 
> > > - output is being done to the device
> > > - a key is being held down (remote wakeup isn't triggered upon key release)
> > > - LED(s) are lit
> > Why we shouldn't autosuspend it if it has LED lit?
> 
> If you suspend LEDs go dark. You'd hit e.g. caps lock, the LED would go
> bright and two seconds later dark. That's no good.
we can set longer intervel to aviod it to autosuspend in short interval.

I don't think lighting LED is one reason we can't autosuspend, display
is a good example for this, the system will suspend to ram or hibernate
if the user leaves very long although display is bright.
> 
> 	Regards
> 		Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-input" 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 Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux