linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yi Yang <yi.y.yang@intel.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Jiri Kosina <jikos@jikos.cz>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [patch]aggessive autosuspend for HID devices (resent due to corruption)
Date: Wed, 29 Oct 2008 02:08:36 +0800	[thread overview]
Message-ID: <1225217316.4017.7.camel@yangyi-dev> (raw)
In-Reply-To: <200810280947.16006.oliver@neukum.org>

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


  reply	other threads:[~2008-10-28 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27  9:42 [patch]aggessive autosuspend for HID devices (resent due to corruption) Oliver Neukum
2008-10-28 10:20 ` Yi Yang
2008-10-28 16:26 ` Yi Yang
2008-10-28  8:47   ` Oliver Neukum
2008-10-28 18:08     ` Yi Yang [this message]
2008-10-28 11:02       ` Oliver Neukum
     [not found] ` <200810271042.37365.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-10-29 13:28   ` Jiri Kosina
2008-10-29 14:06     ` Oliver Neukum
2008-10-29 15:25     ` Oliver Neukum
2008-10-30 23:08       ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1225217316.4017.7.camel@yangyi-dev \
    --to=yi.y.yang@intel.com \
    --cc=jikos@jikos.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).