From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: General PulseAudio Discussion
<pulseaudio-discuss@mail.0pointer.de>,
alsa-devel@alsa-project.org,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org, mzjro@0pointer.de
Subject: Re: [PATCH] thinkpad-acpi: Enable microphone mute LED
Date: Fri, 27 May 2011 19:26:50 +0100 [thread overview]
Message-ID: <20110527182650.GA19697@srcf.ucam.org> (raw)
In-Reply-To: <BANLkTimuXJchtdeV0BT3A=BTvihOFShhwA@mail.gmail.com>
On Fri, May 27, 2011 at 02:22:26PM -0400, Andrew Lutomirski wrote:
> On Fri, May 27, 2011 at 12:48 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > Hm. That makes things kind of tricky. While it's easy to just expose the
> > LED, really we want to do it in such a way that userspace knows which
> > LEDs it should be toggling while setting the microphone mute.
>
> One thought: call the thing laptop::micmute and teach userspace to
> look for an led with that name.
Yes, I think standardised naming is going to be necessary to make this
kind of thing work. That just leaves us with the additional problem of
figuring out who has responsibility for toggling it and maanging
permissions appropriately, but we'll get to that.
> Do any of the ALSA or PulseAudio people have any preferences?
Cc:ed Lennart to get his perspective.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-05-27 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8dc2b2140c2794291811cd38f51f9dc7596f482c.1306266017.git.luto@mit.edu>
[not found] ` <20110527162844.GA16769@srcf.ucam.org>
[not found] ` <BANLkTint5_Vcm5rWKHL_j5XsVmcAu8X7pw@mail.gmail.com>
[not found] ` <20110527164855.GA17443@srcf.ucam.org>
2011-05-27 18:22 ` [PATCH] thinkpad-acpi: Enable microphone mute LED Andrew Lutomirski
2011-05-27 18:26 ` Matthew Garrett [this message]
2011-06-03 15:50 ` [alsa-devel] " 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=20110527182650.GA19697@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alsa-devel@alsa-project.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=luto@mit.edu \
--cc=mzjro@0pointer.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pulseaudio-discuss@mail.0pointer.de \
/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