From: Alex Dewar <alex.dewar@gmx.co.uk>
To: dmitry.torokhov@gmail.com, tiwai@suse.de, hdegoede@redhat.com,
markgross@kernel.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: input/i8042: Malfunctioning brightness keys on HP Elite Dragonfly G2
Date: Tue, 05 Jul 2022 18:28:34 +0100 [thread overview]
Message-ID: <3b9e115d4b8b6f363c45fe510e822e16fbce9a25.camel@gmx.co.uk> (raw)
In-Reply-To: <20220629094314.b7xmfb3xccj7vs6v@ic-alex-elitebook>
Friendly ping? 🙂
I'm also CC'ing the x86 platform people into this, as I'm not sure
whether this problem is something more within their remit.
Best,
Alex
On Wed, 2022-06-29 at 10:43 +0100, Alex Dewar wrote:
> Hi,
>
> I'm running Linux 5.18.7 on an HP Elite Dragonfly G2 laptop, which
> seems
> to use the i8042 driver. Mostly things seem to work (including
> hotkeys)
> except that the increase/decrease brightness keys instead send the
> "mic
> mute" keycode. (The *actual* mic mute key works fine.)
>
> Any ideas? Do we need to add a quirk?
>
> Best,
> Alex
prev parent reply other threads:[~2022-07-05 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220629094314.b7xmfb3xccj7vs6v@ic-alex-elitebook>
2022-07-05 17:25 ` input/i8042: Malfunctioning brightness keys on HP Elite Dragonfly G2 Alex Dewar
2022-07-09 14:56 ` Hans de Goede
2022-07-11 7:49 ` Alex Dewar
2022-07-11 12:09 ` Hans de Goede
2022-07-11 13:10 ` Lopez, Jorge A (Security)
2022-07-11 14:26 ` Lopez, Jorge A (Security)
2022-07-11 14:35 ` Alex Dewar
2022-07-11 14:59 ` Lopez, Jorge A (Security)
2022-07-13 8:16 ` Alex Dewar
2022-07-13 16:34 ` Lopez, Jorge A (Security)
2022-07-14 9:22 ` Alex Dewar
2022-07-05 17:28 ` Alex Dewar [this message]
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=3b9e115d4b8b6f363c45fe510e822e16fbce9a25.camel@gmx.co.uk \
--to=alex.dewar@gmx.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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 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).