All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Andy Lutomirski <luto@amacapital.net>, Takashi Iwai <tiwai@suse.de>
Cc: Grant Diffey <gdiffey@gmail.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Subject: Re: Exposing the ThinkPad HW mute switch to ALSA?
Date: Wed, 08 Oct 2014 08:17:54 +0200	[thread overview]
Message-ID: <5434D712.4060401@canonical.com> (raw)
In-Reply-To: <CALCETrXhforbHXNGzC77LxP+thUADpxVEosU6fHf-V5JAWV8vA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

On 2014-10-08 02:43, Andy Lutomirski wrote:
> Admittedly, I see some value in having the mute button mute things
> regardless of what userspace is doing, but I don't see *much* value in
> it.  And, arguably, if that behavior is actually desirable, it should
> be available on all laptops, not just ThinkPads.

Things start to get tricky when you think one step ahead and ask 
yourself what outputs the button and the LED really should control. We 
touched the topic briefly when discussing LEDs on the audio meeting last 
year. I'm attaching my presentation for reference.

(The outcome of the discussion about the mic mute LED was "we don't 
know, go ask designers", and well, you probably know the result, as we 
ended up with "The internal card's mics" for the mic mute LED.)

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

[-- Attachment #2: mic-mute-LED.pdf --]
[-- Type: application/pdf, Size: 30456 bytes --]

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2014-10-08  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALCETrULBrany=JLyZsfq6oiGDDUZOZyA+=7=GqLW8h+ZoHJVA@mail.gmail.com>
2014-10-06 13:04 ` Exposing the ThinkPad HW mute switch to ALSA? Takashi Iwai
2014-10-06 19:09   ` Henrique de Moraes Holschuh
2014-10-07  0:06     ` Andy Lutomirski
2014-10-07  5:25       ` Takashi Iwai
2014-10-07  6:25         ` Grant Diffey
2014-10-07  9:59           ` Takashi Iwai
2014-10-07 13:19             ` Henrique de Moraes Holschuh
2014-10-07 14:44               ` Andy Lutomirski
2014-10-07 14:50                 ` Takashi Iwai
2014-10-08  0:43                   ` Andy Lutomirski
2014-10-08  5:19                     ` Takashi Iwai
2014-10-08  6:17                     ` David Henningsson [this message]
2014-10-07 13:12           ` Henrique de Moraes Holschuh

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=5434D712.4060401@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=gdiffey@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=luto@amacapital.net \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.