From: Jerone Young <jerone.young@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Fix mute key on older Thinkpads by OSI blacklisting them
Date: Sun, 25 Apr 2010 13:57:52 -0500 [thread overview]
Message-ID: <1272221872.1640.22.camel@laptop> (raw)
In-Reply-To: <20100425184405.GA29130@srcf.ucam.org>
On Sun, 2010-04-25 at 19:44 +0100, Matthew Garrett wrote:
> On Sun, Apr 25, 2010 at 01:28:11PM -0500, Jerone Young wrote:
>
> > I think it's not really possible to get it correct with thinkpad-acpi .
> > The reason is the userspace sound server. In our case it's pulse audio.
> > So we are no longer just dealing with ALSA anymore. So if the OS gets a
> > proper hotkey event it is able to mute at the pulse audio level then,
> > pulse audio does work at the ALSA level (toggling the mixer).
> > thinkpad-acpi has no way to check on the status of pulse audio.
>
> This really isn't a problem. We have a mixer device for the Thinkpad's
> own mixer, and we can send ALSA events to indicate that its state has
> changed.
I think it is. Since pulse audio only pay attention to the Master mixer
of the primary card. The Thinkpad EC shows up basically as a second
audio card.
But again new Thinkpads don't need this. Since they send a soft keypress
by default. So userspace catches it and changes the Master mixer to
mute.
I think all this work isn't going to help the situation any. There
appears to be a easy solution. Just a matter of getting the LEDs on some
to light correctly, and see when the hardware mute is enabled.
Thanks,
Jerone
>
next prev parent reply other threads:[~2010-04-25 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 22:48 [PATCH] Fix mute key on older Thinkpads by OSI blacklisting them Jerone Young
2010-04-24 2:01 ` Henrique de Moraes Holschuh
2010-04-24 2:14 ` Jerone Young
2010-04-24 2:19 ` Jerone Young
2010-04-24 3:10 ` Henrique de Moraes Holschuh
2010-04-24 4:15 ` Jerone Young
2010-04-24 16:01 ` Matthew Garrett
2010-04-24 20:49 ` Jerone Young
2010-04-24 21:16 ` Matthew Garrett
2010-04-25 0:08 ` Jerone Young
2010-04-25 2:28 ` Henrique de Moraes Holschuh
2010-04-25 18:28 ` Jerone Young
2010-04-25 18:44 ` Matthew Garrett
2010-04-25 18:57 ` Jerone Young [this message]
2010-04-25 18:59 ` Matthew Garrett
2010-04-25 19:19 ` Jerone Young
2010-04-26 10:11 ` Henrique de Moraes Holschuh
2010-04-27 5:50 ` Jerone Young
2010-04-25 19:02 ` Jerone Young
2010-04-26 10:38 ` Henrique de Moraes Holschuh
2010-04-27 5:44 ` Jerone Young
2010-04-25 0:19 ` Jerone Young
2010-05-03 11:45 ` Andy Lutomirski
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=1272221872.1640.22.camel@laptop \
--to=jerone.young@canonical.com \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).