From: Rhys Perry <rhysperry111@gmail.com>
To: platform-driver-x86@vger.kernel.org
Subject: Re: [hp_wmi] Recieving same keycode from two keys
Date: Tue, 3 Nov 2020 08:34:54 +0000 [thread overview]
Message-ID: <CAGTBY+sgwYrDPtQgJV=TcXJ73n8TGf9Nw=arCfWMUrVFzAsEVQ@mail.gmail.com> (raw)
In-Reply-To: <Q5ZWCQ.DX8TK304ORAI@gmail.com>
On Fri, 3 Jul 2020 at 23:22, <rhysperry111@gmail.com> wrote:
>
> Hi,
>
> I would just like to preface this by saying that I am no too familiar
> with mailing list etiquette so I am sorry if I break any rules.
>
> I have a laptop with dedicated brighness keys (HP Pavilion
> 15-cx0598na). I believe these keys are handled by hp_wmi.
>
> Whenever I press (and release) one of the brightness keys, this message
> appears in the journal:
> ```
> [50761.461630] atkbd serio0: Unknown key pressed (translated set 2,
> code 0xab on isa0060/serio0).
> [50761.461637] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> it known.
> [50761.492161] atkbd serio0: Unknown key released (translated set 2,
> code 0xab on isa0060/serio0).
> [50761.492168] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> it known.
> ```
> Now, this is not that interesting at first, I obviously just need to
> map a keycode. The confusing part is that for both the brightness up
> AND the brightness down key I get the same code (e02b). I am not to
> sure how to debug this behavior but I would appreciate if someone
> helped investigate this issue.
>
> I am not sure if this is relevant, but my RFKILL key does not work
> either (but does not show anything in journal).
>
> Here is a link to acpidump:
> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>
> ::: Rhys Perry :::
Sorry if this is breaking kernel mailing list etiquette, but I am
posting this question again as I did not get a response last time.
next parent reply other threads:[~2020-11-03 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Q5ZWCQ.DX8TK304ORAI@gmail.com>
2020-11-03 8:34 ` Rhys Perry [this message]
2020-11-03 9:53 ` [hp_wmi] Recieving same keycode from two keys Barnabás Pőcze
[not found] ` <CAGTBY+vQ+UMPqFCwKMS0L5=F3eqQ21UtGETgmE+Le=SXcaWS2w@mail.gmail.com>
[not found] ` <bjucdDbwHvavLvYVkhboo_jhvKC6ccqAslFPuuYO0ZZcgTZZaICda3WMFZhw_zS1o1m7VanyCmaJ4HZMqgyXwsCfqJFDGxb_1A4pdNCe8Bw=@protonmail.com>
[not found] ` <CAGTBY+tso9BKJwe5F5bBU_RAo0yrwtYf=kGm1UvMpTJurS00MQ@mail.gmail.com>
2020-11-03 13:06 ` Barnabás Pőcze
2020-11-03 13:35 ` Rhys Perry
2020-11-03 14:16 ` Hans de Goede
2020-11-03 14:38 ` Rhys Perry
[not found] ` <CAGTBY+u_=5Po2qTPuunmK+sxE8sJ3Z1jcQXjiTcMb7V2iVwSjA@mail.gmail.com>
2020-11-03 14:43 ` Hans de Goede
2020-11-03 14:51 ` Rhys Perry
2020-11-03 15:20 ` Hans de Goede
2020-11-03 15:43 ` Rhys Perry
2020-11-03 17:46 ` Hans de Goede
2020-11-24 11:13 ` Hans de Goede
2020-11-24 13:28 ` Rhys Perry
2020-11-24 13:33 ` 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='CAGTBY+sgwYrDPtQgJV=TcXJ73n8TGf9Nw=arCfWMUrVFzAsEVQ@mail.gmail.com' \
--to=rhysperry111@gmail.com \
--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 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).