LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Daniel Perzynski <daniel.perzynski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HP WMI laptop extras driver
Date: Fri, 28 Nov 2008 16:12:49 +0000	[thread overview]
Message-ID: <20081128161249.GA6865@srcf.ucam.org> (raw)
In-Reply-To: <28f715610811221340s5911bf20mf763f0e6990c7078@mail.gmail.com>

On Sat, Nov 22, 2008 at 10:40:17PM +0100, Daniel Perzynski wrote:

> Nov 22 13:11:49 h3xu5 input: HP WMI hotkeys as /class/input/input9
> quickplay button -> Nov 22 13:13:10 h3xu5 HP WMI: Unknown key pressed - 22142
> quickplay dvd button  -> Nov 22 13:14:22 h3xu5 HP WMI: Unknown key pressed -
> 220e6
> quickplay TV button -> Nov 22 13:14:52 h3xu5 HP WMI: Unknown key pressed -
> 22181

Hm. I /suspect/ that these would be better handled by a quickplay button 
driver. There's a patch for that lying around - I'll try to get it 
updated.

> previous track button -> Nov 22 13:15:50 h3xu5 HP WMI: Unknown key pressed -
> 32192
> stop button -> Nov 22 13:16:15 h3xu5 HP WMI: Unknown key pressed - 32191
> play/pause button -> Nov 22 13:16:30 h3xu5 HP WMI: Unknown key pressed - 32190
> next track  button -> Nov 22 13:16:46 h3xu5 HP WMI: Unknown key pressed - 32193
> 
> 4 above buttons are working fine in x-windows

Ok, so again handling them in hp-wmi is probably not a good idea.

> As I understand wifi on/off is supported already by hp-wmi driver

Yup.

> sound mute button -> Nov 22 13:23:28 h3xu5 HP WMI: Unknown key pressed - 32190
> volume up -> Nov 22 13:24:02 h3xu5 HP WMI: Unknown key pressed - 32190
> volume down -> Nov 22 13:24:04 h3xu5 HP WMI: Unknown key pressed - 32190
> 
> above 3 are working fine in x-windows

Since they're going through the keyboard controller, we should probably 
ignore them.

> bass/treble switch button -> Nov 22 13:25:06 h3xu5 HP WMI: Unknown key pressed
> - 22199
> bass/treble up button:
> Nov 22 13:26:18 h3xu5 HP WMI: Unknown key pressed - 22197
> Nov 22 13:26:18 h3xu5 atkbd.c: Unknown key pressed (translated set 2, code 0xbe
> on isa0060/serio0).
> Nov 22 13:26:18 h3xu5 atkbd.c: Use 'setkeycodes e03e <keycode>' to make it
> known.
> bass/treble down button:
> Nov 22 13:26:21 h3xu5 HP WMI: Unknown key pressed - 22198
> Nov 22 13:26:21 h3xu5 atkbd.c: Unknown key pressed (translated set 2, code 0xbf
> on isa0060/serio0).
> Nov 22 13:26:21 h3xu5 atkbd.c: Use 'setkeycodes e03f <keycode>' to make it
> known.
> cd eject button -> Nov 22 13:26:45 h3xu5 HP WMI: Unknown key pressed - 0

Again, looks like these are going through the keyboard controller. 
Thanks for the feedback, I'll try to work out a way of avoiding printing 
the messages.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

       reply	other threads:[~2008-11-28 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28f715610811221340s5911bf20mf763f0e6990c7078@mail.gmail.com>
2008-11-28 16:12 ` Matthew Garrett [this message]
2008-11-22 21:43 Daniel Perzynski
2008-11-28 17:19 ` Matthew Garrett
     [not found] <28f715610810310624m67b86d10t76b21b2cbbf2a8ac@mail.gmail.com>
2008-10-31 13:28 ` Matthew Garrett

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=20081128161249.GA6865@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=daniel.perzynski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: HP WMI laptop extras driver' \
    /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

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).