From: Pavel Machek <pavel@ucw.cz>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, mjg@redhat.com, rjw@sisk.pl,
len.brown@intel.com, dtor@insightbb.com
Subject: Re: [PATCH 1/3] Input: atkbd - add LED triggers for keyboard state
Date: Sun, 22 Sep 2013 16:26:29 +0200 [thread overview]
Message-ID: <20130922142629.GA30282@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1377180132-4933-1-git-send-email-Jason@zx2c4.com>
Hi!
> Many new laptop keyboards aren't shipping with LEDs in the keys for
> caps lock, num lock, and scroll lock. They do, however, ship with many LEDs
> for specialized functions that mostly go non-utilized by any current
> Linux drivers. Having a caps lock LED is very helpful in early boot full
> disk encryption, where a fancy GUI is not available to show that caps
> lock is activated.
>
> This patch wires in the caps, num, and scroll lock states of the
> keyboard into the generic LED trigger subsystem, so that integrators can
> have different LEDs activated on caps/num/scroll lock state changes.
There's another patch floating around that properly integrates input
with LED subsystem; it already contains this functionality IIRC.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2013-09-22 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 14:02 [PATCH 1/3] Input: atkbd - add LED triggers for keyboard state Jason A. Donenfeld
2013-08-22 14:02 ` [PATCH 2/3] thinkpad_acpi: Support micmute LED Jason A. Donenfeld
2013-08-23 18:16 ` Henrique de Moraes Holschuh
2013-08-22 14:02 ` [PATCH 3/3] thinkpad_acpi: Wire unused micmute LED to capslock Jason A. Donenfeld
2013-08-22 15:39 ` Matthew Garrett
2013-08-22 17:29 ` Jason A. Donenfeld
2013-08-23 18:18 ` Henrique de Moraes Holschuh
2013-08-24 20:29 ` Jason A. Donenfeld
2013-09-22 14:26 ` Pavel Machek [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=20130922142629.GA30282@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=Jason@zx2c4.com \
--cc=dtor@insightbb.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
/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).