linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Alex Dewar <alex.dewar@gmx.co.uk>,
	dmitry.torokhov@gmail.com, tiwai@suse.de, markgross@kernel.org,
	"Lopez, Jorge A (Thin Clients)" <jorge.lopez2@hp.com>
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: Mon, 11 Jul 2022 14:09:58 +0200	[thread overview]
Message-ID: <c89d39eb-17b9-8800-c8ff-8d236b80de2f@redhat.com> (raw)
In-Reply-To: <df7313597d2ac3212f10c05aa3d369728f030c86.camel@gmx.co.uk>

Hi Alex,

On 7/11/22 09:49, Alex Dewar wrote:
> Hi Hans,
> 
> On Sat, 2022-07-09 at 16:56 +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 7/5/22 19:25, Alex Dewar wrote:
>>> 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.
>>
>> Please test the atbkd device with "sudo evemu-record" or "sudo
>> evtest"
>> and if the brightness keys generate events there, write down the
>> raw event codes (MSC events).
> 
> I tried this but unfortunately this doesn't seem to be the whole story.
> If I press "decrease brightness" I get:
> Event: time 1657525393.922727, -------------- SYN_REPORT ------------
> Event: time 1657525397.043348, type 4 (EV_MSC), code 4 (MSC_SCAN),
> value 81
> Event: time 1657525397.043348, type 1 (EV_KEY), code 190 (KEY_F20),
> value 1
> Event: time 1657525397.043348, -------------- SYN_REPORT ------------
> Event: time 1657525397.050384, type 4 (EV_MSC), code 4 (MSC_SCAN),
> value 81
> Event: time 1657525397.050384, type 1 (EV_KEY), code 190 (KEY_F20),
> value 0
> 
> And if I press "increase brightness" I get:
> Event: time 1657525397.050384, -------------- SYN_REPORT ------------
> Event: time 1657525398.607184, type 4 (EV_MSC), code 4 (MSC_SCAN),
> value 81
> Event: time 1657525398.607184, type 1 (EV_KEY), code 190 (KEY_F20),
> value 1
> Event: time 1657525398.607184, -------------- SYN_REPORT ------------
> Event: time 1657525398.614190, type 4 (EV_MSC), code 4 (MSC_SCAN),
> value 81
> Event: time 1657525398.614190, type 1 (EV_KEY), code 190 (KEY_F20),
> value 0
> 
> There's no difference! And I also get the same thing if I press the
> *actual* mute mic button 😞.
> 
> Any ideas?

From this it looks like we need to use some other interface to get
these events (+ ignore the above events).

Do you have a "HP WMI hotkeys" device in your list of input
devices?  And are you getting any events on that ?

Likewise do you have a "Video Bus" device and any events on that ?

I've also added Jorge from HP to the Cc. Jorge, can you help with this ?

Regards,

Hans


  reply	other threads:[~2022-07-11 12:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  9:43 input/i8042: Malfunctioning brightness keys on HP Elite Dragonfly G2 Alex Dewar
2022-07-05 17:25 ` 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 [this message]
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

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=c89d39eb-17b9-8800-c8ff-8d236b80de2f@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alex.dewar@gmx.co.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jorge.lopez2@hp.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).