From: Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
To: yi.y.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: Jiri Kosina <jikos-wDf7oJUeT2I@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch]aggessive autosuspend for HID devices (resent due to corruption)
Date: Tue, 28 Oct 2008 09:47:15 +0100 [thread overview]
Message-ID: <200810280947.16006.oliver@neukum.org> (raw)
In-Reply-To: <1225211162.4017.1.camel@yangyi-dev>
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.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-28 8:47 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 [this message]
2008-10-28 18:08 ` Yi Yang
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=200810280947.16006.oliver@neukum.org \
--to=oliver-gvhc2dphhpqdnm+yrofe0a@public.gmane.org \
--cc=jikos-wDf7oJUeT2I@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yi.y.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).