From: Jens Taprogge <jens.taprogge@taprogge.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] [thinkpad-acpi] Add T410s and T420s LED support
Date: Fri, 23 Mar 2012 21:07:38 +0100 [thread overview]
Message-ID: <20120323200738.GA3840@endeavour.taprogge.org> (raw)
In-Reply-To: <20120323194355.GA27877@srcf.ucam.org>
On Fri, Mar 23, 2012 at 07:43:55PM +0000, Matthew Garrett wrote:
> I'm a little unenthusiastic about just pulling this in without working
> out how userspace is going to consume it. It's a problem we may hit on
> other devices as well, so we potentially need some sort of consistent
> naming to indicate that it's a built-in mute LED.
Would a name like "laptop_mute_mic" be more descriptive? Please note
that with the patch the LED only exposed if
CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is set. (And so are other like for
example the battery LEDs.)
If possible, I think it would be good to generally handle the LED in
kernel space. Otherwise, the risk of the LED getting out of sync with
the actually muting is just to big. I am not sure how that could be
achieved though. Basically ALSA would have to expose some kind of hook
that thinkpad_acpi (or other users) could connect to.
Best Regards
-Jens
next prev parent reply other threads:[~2012-03-23 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 23:49 [PATCH] [thinkpad-acpi] Add T410s and T420s LED support Jens Taprogge
2012-03-23 19:39 ` Henrique de Moraes Holschuh
2012-03-23 19:43 ` Matthew Garrett
2012-03-23 20:07 ` Jens Taprogge [this message]
2012-03-23 23:38 ` Henrique de Moraes Holschuh
2012-03-24 0:05 ` Jens Taprogge
2012-03-24 2:50 ` Henrique de Moraes Holschuh
2012-03-24 15:44 ` Jens Taprogge
2012-03-28 16:16 ` Takashi Iwai
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=20120323200738.GA3840@endeavour.taprogge.org \
--to=jens.taprogge@taprogge.org \
--cc=hmh@hmh.eng.br \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.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