X86 platform drivers
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
	ibm-acpi-devel@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] thinkpad-acpi: Enable microphone mute LED
Date: Fri, 27 May 2011 17:48:55 +0100	[thread overview]
Message-ID: <20110527164855.GA17443@srcf.ucam.org> (raw)
In-Reply-To: <BANLkTint5_Vcm5rWKHL_j5XsVmcAu8X7pw@mail.gmail.com>

On Fri, May 27, 2011 at 12:39:10PM -0400, Andrew Lutomirski wrote:

> I don't have docs so I don't really know.  But the mute LED does not
> appear to be controllable from the LED interface and when mute is lit
> there's no sound regardless of what ALSA thinks.  When I light the
> micmute light, I can still record sound just fine.
> 
> The mic mute button does nothing on Windows unless the special driver
> is installed, and that driver seems to mute the Windows mixer, so I
> think there's nothing special other than a little userspace helper
> going on.

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.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-05-27 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 19:41 [PATCH] thinkpad-acpi: Enable microphone mute LED Andy Lutomirski
2011-05-27 16:28 ` Matthew Garrett
2011-05-27 16:39   ` Andrew Lutomirski
2011-05-27 16:48     ` Matthew Garrett [this message]
2011-05-27 18:22       ` Andrew Lutomirski
2011-05-27 18:26         ` Matthew Garrett
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=20110527164855.GA17443@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=luto@mit.edu \
    --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