From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC PATCH] thinkpad-acpi: Improve hardware volume controls
Date: Thu, 12 May 2011 15:39:12 +0100 [thread overview]
Message-ID: <20110512143912.GA28141@srcf.ucam.org> (raw)
In-Reply-To: <BANLkTimmrM4HMATSbsYzz6kh=e9hrfAZmg@mail.gmail.com>
On Thu, May 12, 2011 at 10:24:10AM -0400, Andrew Lutomirski wrote:
> On Thu, May 12, 2011 at 9:48 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > It looks like SAUM was introduced with the *61 machines, and it's
> > identical from then on.
>
> I wonder the machines with SAUM are the same as the machines on which
> pressing mute generates an i8042 keystroke instead of an HKEY. If so,
> it looks like there's some code (or at least comments) in
> thinkpad_acpi that mention doing the right thing when the HKEY mute
> event in generated (e.g. the driver won't send KEY_MUTE to the input
> layer), so something like my patch along with removing the _OSI(Linux)
> hack for the newer models might make everything work right.
I think so. The machines we have in the OSI blacklist all appear to have
the SAUM method, so I think we can take your patch and drop the
blacklist. Good work!
> Still, someone who has an older laptop should test it, because all I
> can do is pretend I carefully inspected all the possible code paths.
I can't see any way this would cause problems, except in the case where
the method exists but doesn't do anything. I'd be surprised if that's a
real problem.
> (Even if it works, don't apply this patch for 2.6.40 as it stands
> because the ALSA change notification on KEY_MUTE is crap and should at
> least ignore key release events.)
Are you working with the ALSA people on that?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-05-12 14:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 22:18 [RFC PATCH] thinkpad-acpi: Improve hardware volume controls Andy Lutomirski
2011-05-09 23:53 ` Henrique de Moraes Holschuh
2011-05-10 0:38 ` Andrew Lutomirski
2011-05-10 1:04 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2011-05-10 2:36 ` Andrew Lutomirski
2011-05-10 3:41 ` Andrew Lutomirski
2011-05-10 10:27 ` Henrique de Moraes Holschuh
2011-05-10 10:39 ` Andrew Lutomirski
[not found] ` <BANLkTikgKj9yBUTLiFVj4tP2LNSzbExo1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-10 10:44 ` [PATCH v2] " Andy Lutomirski
2011-05-10 10:25 ` [ibm-acpi-devel] [RFC PATCH] " Henrique de Moraes Holschuh
2011-05-12 13:48 ` Matthew Garrett
2011-05-12 14:24 ` Andrew Lutomirski
2011-05-12 14:39 ` Matthew Garrett [this message]
2011-05-12 14:50 ` Andrew Lutomirski
[not found] ` <BANLkTikX7mMu2me6+O1e-Ub=Cbzerd=J3Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-12 15:39 ` Dmitry Torokhov
2011-05-12 19:33 ` Andrew Lutomirski
2011-05-12 20:42 ` Dmitry Torokhov
2011-05-14 15:34 ` [PATCH v3] " Andy Lutomirski
2011-05-14 15:47 ` Matthew Garrett
2011-05-14 15:55 ` Andrew Lutomirski
2011-05-14 18:41 ` Henrique de Moraes Holschuh
2011-05-15 19:22 ` Andrew Lutomirski
2011-05-12 21:43 ` [RFC PATCH] " Henrique de Moraes Holschuh
2011-05-16 13:49 ` [PATCH v4] " 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=20110512143912.GA28141@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--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 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.