All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dennis Nezic" <dennisn@dennisn.mooo.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: hp-wmi: info hotkey has no keycode or scancode
Date: Sat, 20 Jan 2024 16:39:38 -0500	[thread overview]
Message-ID: <Zaw9mnfEL65B5r4O@panther> (raw)
In-Reply-To: <a8fa0308-0998-48e4-a104-c2b57ee9bd8e@gmx.de>

On 20 Jan 21:52, Armin Wolf wrote:
> Am 20.01.24 um 19:58 schrieb Dennis Nezic:
> 
> > Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't
> > work", showkey doesn't report any keycode or scancode. I don't see any
> > wmi related error messages from dmesg. All the other illuminated
> > "hotkeys" work fine, although confusingly evtest and "libinput
> > debug-events" report that they're coming through the event interface
> > associated with "AT Translated Set 2 keyboard" instead of "HP WMI
> > hotkeys", but hey, as long as I receive them I'm okay :p.
> >
> > hp-wmi.c does seem to reference it:
> >    { KE_KEY, 0x213b,  { KEY_INFO } },
> >
> > How can I go about troubleshooting this? (I'm using kernel 6.6.8)
> 
> it can be possible that your machine does not use hp-wmi to deliver keycodes
> to the operating system, but instead emulates a standard keyboard controller.
> 
> Can you check with "kacpimon" that events concerning a PNP0C14 device are being
> received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

  reply	other threads:[~2024-01-20 21:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 18:58 hp-wmi: info hotkey has no keycode or scancode Dennis Nezic
2024-01-20 20:52 ` Armin Wolf
2024-01-20 21:39   ` Dennis Nezic [this message]
2024-01-21 15:16     ` Armin Wolf
2024-01-22  7:05       ` Dennis Nezic
2024-01-22 10:44         ` Armin Wolf
     [not found]           ` <Za8xL39m1X22f2Bb@panther>
     [not found]             ` <Za9DQdLg2d_CnrZG@panther>
2024-01-23  8:58               ` Armin Wolf
2024-01-23 14:22                 ` Armin Wolf
2024-01-23 15:13                   ` Dennis Nezic
2024-01-23 15:34                     ` Hans de Goede
2024-01-23 19:58                       ` Armin Wolf
2024-01-25 20:53                         ` Armin Wolf
2024-01-29 13:00                           ` Hans de Goede
2024-01-29 12:57                         ` Hans de Goede
2024-03-26 16:47                           ` Dennis Nezic
2024-01-30 18:18                         ` Dennis Nezic
2024-01-31  4:06                           ` Dennis Nezic
2024-01-30 20:20                         ` Dennis Nezic
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31  4:01 Dennis Nezic

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=Zaw9mnfEL65B5r4O@panther \
    --to=dennisn@dennisn.mooo.com \
    --cc=W_Armin@gmx.de \
    --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.