From: Dmitry Torokhov <dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Cc: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
Jiri Kosina <jikos-AlSwsSmVLrQ@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Keyboard LED state after suspend
Date: Thu, 13 Nov 2008 16:52:53 -0500 [thread overview]
Message-ID: <20081113165230.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <200811132208.37874.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
On Thu, Nov 13, 2008 at 10:08:37PM +0100, Oliver Neukum wrote:
> Am Donnerstag, 13. November 2008 21:05:39 schrieb Alan Stern:
> > Jiri and Oliver:
> >
> > I tried the experiment of turning off NumLock and all the other
> > keyboard LED settings before hibernating. After resuming, the LEDs on
> > my PS/2 keyboard remained off but the NumLock LED on my USB keyboard
> > was on. Probably the BIOS turned it on during the restart and Linux
> > never turned it back off.
> >
> > Should we set the keyboard LED state whenever a keyboard is resumed?
> > Is this handled already in the new autosuspend work?
>
> No, as this is no autosuspend problem. In fact it is not a driver problem
> at all. This suggests that the HID layer should have hooks in resumption.
>
Actually I have patches that do that in input layer.
--
Dmitry
--
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
prev parent reply other threads:[~2008-11-13 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 20:05 Keyboard LED state after suspend Alan Stern
[not found] ` <Pine.LNX.4.44L0.0811131501250.3036-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2008-11-13 21:08 ` Oliver Neukum
[not found] ` <200811132208.37874.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-11-13 21:52 ` Dmitry Torokhov [this message]
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=20081113165230.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jikos-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@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).