From: Matthew Garrett <mjg59@srcf.ucam.org>
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 3/3] thinkpad_acpi: Wire unused micmute LED to capslock
Date: Thu, 22 Aug 2013 16:39:00 +0100 [thread overview]
Message-ID: <20130822153900.GA2878@srcf.ucam.org> (raw)
In-Reply-To: <1377180132-4933-3-git-send-email-Jason@zx2c4.com>
On Thu, Aug 22, 2013 at 04:02:12PM +0200, Jason A. Donenfeld wrote:
> Thinkpads with a micmute LED do not have a capslock LED. The micmute LED
> is currently not used by any piece of Linux kernel land or user land. It
> seems reasonable to hook it up to caps lock, at least by default, so
> users can have some degree of functionality.
I think there's a risk of user confusion here, in that it's now possible
for the mic mute light to be lit despite the internal microphone still
being active. That seems like surprising behaviour.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-08-22 15:39 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 [this message]
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 ` [PATCH 1/3] Input: atkbd - add LED triggers for keyboard state Pavel Machek
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=20130822153900.GA2878@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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).