All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>, thestroyer@cock.li
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
	Mark Gross <mgross@linux.intel.com>
Subject: Re: HP Zbook studio G5 Brightness and mic mute keys give same scancode
Date: Mon, 9 Nov 2020 14:44:08 +0100	[thread overview]
Message-ID: <97c507c1-21a9-2b77-5d07-09cfcd93ca39@redhat.com> (raw)
In-Reply-To: <CAHp75VfTXieJws5gB70L5grsc0f_SFo+sNv1ySmt37aOUa6TmA@mail.gmail.com>

Hi,

On 11/5/20 5:47 PM, Andy Shevchenko wrote:
> +Cc: subsystem maintainers
> 
> On Sun, May 17, 2020 at 2:24 PM <thestroyer@cock.li> wrote:
>>
>> Hi,
>> On my HP Zbook studio G5 a few keys on my keyboard give the same
>> scancodes. Most notably, the brightness and mute function keys all give
>> the scan code sequence 0xe0 0x20 0xe0 0xa0 as reported by showkey
>> --scancodes. It only produces a scancode when pressed, not when
>> released. I found another very similar issue in this mailing list found
>> in https://www.spinics.net/lists/platform-driver-x86/msg16791.html. The
>> issue in that mail was solved by a bios update. I'm running the latest
>> bios, but I still have the issue.
>> I tried the kernels: Manjaro 5.7rc4-1, Manjaro 5.6.11-1 and Manjaro
>> 5.4.39-1
>> I also tried a few other distributions, but they all have the same
>> issue.
>> I'm happy to provide more information about this issue if needed.

So this already came in another thread for another HP laptop model,
this seems to be a common issue on some (newer?) HP laptop models.

It seems that we need to make some special WMI calls for this, either
to figure out which key is actually pressed when receiving the
PS/2 scancode which is shared between multiple keys. Or to get the
device to send different scancodes.

This will require someone with some knowledge of ACPI/WMI as well
as of writing kernel code to get physical access to an affected HP
laptop to figure out what is going on and write some code to deal with
this special setup.

Regards,

Hans


  reply	other threads:[~2020-11-09 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d2753cb4ca4d0d819d5a76b0a076e281@cock.li>
2020-11-05 16:47 ` HP Zbook studio G5 Brightness and mic mute keys give same scancode Andy Shevchenko
2020-11-09 13:44   ` Hans de Goede [this message]
     [not found]     ` <1dbe090f-03c4-f003-6c38-c139c38313e2@cock.li>
2020-11-24 11:14       ` Hans de Goede
2020-12-04 13:05         ` TheStroyer
2020-12-05 14:49           ` Hans de Goede
2020-12-05 18:21             ` Friso Smit
2020-12-05 18:50               ` Hans de Goede
     [not found]                 ` <230c6976-c3f8-865f-f2b9-82d7de03e07f@cock.li>
2020-12-07 13:40                   ` Hans de Goede

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=97c507c1-21a9-2b77-5d07-09cfcd93ca39@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=thestroyer@cock.li \
    /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.