From: Matthew Garrett <matthew.garrett@nebula.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Tim Chen <tim.chen119@canonical.com>,
"ibm-acpi@hmh.eng.br" <ibm-acpi@hmh.eng.br>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"ibm-acpi-devel@lists.sourceforge.net"
<ibm-acpi-devel@lists.sourceforge.net>,
Alex Hung <alex.hung@canonical.com>, YK <yk@canonical.com>
Subject: Re: [PATCH 0/2] add sysfs for acpi interfaces of thinkpad hardware mute
Date: Wed, 14 Aug 2013 21:15:57 +0000 [thread overview]
Message-ID: <1376514957.28002.13.camel@x230.lan> (raw)
In-Reply-To: <520BEFC4.4030203@canonical.com>
On Wed, 2013-08-14 at 22:59 +0200, David Henningsson wrote:
> On 08/14/2013 10:38 PM, Matthew Garrett wrote:
> > The user hit the mute key. Why would they expect *anything* to be
> > unmuted?
> >
>
> Why should the userspace application, who just wants to lit a LED, have
> to care about a lot of other sound cards and interfaces and mute them,
> when the user does not care?
Because there's no interface for the userspace application to light an
LED. Henrique has previously said that he doesn't want userspace to have
arbitrary control over it, and I agree with him.
> And what about multiseat setups? If a multiseat keyboard has a mic mute
> LED, do you think another user's mic mute state should influence the LED
> of your keyboard?
Once we see an external keyboard with a microphone mute LED, that's
certainly something we can worry about.
--
Matthew Garrett <matthew.garrett@nebula.com>
next prev parent reply other threads:[~2013-08-14 21:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 5:40 [PATCH 0/2] add sysfs for acpi interfaces of thinkpad hardware mute Alex Hung
2013-08-14 5:40 ` [PATCH 1/2] thinkpad-acpi: add sysfs for getting and setting " Alex Hung
2013-08-14 5:40 ` [PATCH 2/2] thinkpad-acpi: add sysfs for enabling and disabling " Alex Hung
[not found] ` <1376458802-11923-1-git-send-email-alex.hung-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-08-14 5:42 ` [PATCH 0/2] add sysfs for acpi interfaces of thinkpad " Matthew Garrett
2013-08-14 5:53 ` Alex Hung
2013-08-14 5:54 ` Matthew Garrett
2013-08-14 6:11 ` Alex Hung
2013-08-14 6:14 ` Matthew Garrett
2013-08-14 6:41 ` Alex Hung
2013-08-14 7:00 ` Matthew Garrett
2013-08-14 7:08 ` Alex Hung
[not found] ` <CAJ=jqubWWeWH+xsGrTVaNguNuw7gm2E=CZmXY_SxO+Bxg1Hxag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-14 23:30 ` Henrique de Moraes Holschuh
2013-08-14 7:16 ` Alex Hung
2013-08-14 7:43 ` David Henningsson
2013-08-14 7:51 ` Matthew Garrett
2013-08-14 9:27 ` David Henningsson
2013-08-14 14:57 ` Matthew Garrett
2013-08-14 19:53 ` David Henningsson
2013-08-14 20:05 ` Matthew Garrett
2013-08-14 20:36 ` David Henningsson
2013-08-14 20:38 ` Matthew Garrett
2013-08-14 20:59 ` David Henningsson
2013-08-14 21:15 ` Matthew Garrett [this message]
2013-08-15 14:55 ` David Henningsson
2013-08-15 14:24 ` [alsa-devel] " Arun Raghavan
[not found] ` <CAJ=jqub1sRSzBRv_R6soDVAydRL+5nmA9-pMC4E+sgXhP6tbPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-14 6:15 ` Alex Hung
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=1376514957.28002.13.camel@x230.lan \
--to=matthew.garrett@nebula.com \
--cc=alex.hung@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tim.chen119@canonical.com \
--cc=yk@canonical.com \
/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.