X86 platform drivers
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: platform-driver-x86@vger.kernel.org
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Subject: [dell-wmi] Dell Vostro 3360 extra multimedia keys don't work
Date: Tue, 15 Apr 2014 00:29:52 +0300	[thread overview]
Message-ID: <1498861.9DHIbmNtA9@spock> (raw)

Hello.

Got Dell Vostro 3360 with extra multimedia keys as shown here [1], but no luck 
to get them work.

While pressing keys "1" and/or "2" I get the following notice in dmesg:

===
dell_wmi: Unknown key e0f0 pressed
===

On pressing key "3" I get the following:

===
atkbd serio0: Unknown key pressed (translated set 2, code 0x60 on 
isa0060/serio0).
atkbd serio0: Use 'setkeycodes 60 <keycode>' to make it known.
===

Watching /proc/interrupts shows that this line:

===
9:      29836        223         96         48   IO-APIC-fasteoi   acpi
===

increments by 2 on pressing each key, and this line:

===
  1:     431013      24838       2688       2270   IO-APIC-edge      i8042
===

Also increments by 1 on pressing key "3".

Running evtest produces the following output [2] with to reaction on keys 
pressing.

acpidump output is also here [3].

Could this be fixed?

[1] 
http://beta.hstor.org/files/c3b/a26/628/c3ba26628409486f8b9ae16d97be7d21.jpg
[2] https://gist.github.com/10683923
[3] https://gist.github.com/10683992

-- 
Oleksandr post-factum Natalenko, MSc
pf-kernel community
https://natalenko.name/

             reply	other threads:[~2014-04-14 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 21:29 Oleksandr Natalenko [this message]
2014-04-14 21:33 ` [dell-wmi] Dell Vostro 3360 extra multimedia keys don't work Matthew Garrett
2014-04-14 21:37   ` Oleksandr Natalenko
2014-04-14 21:57     ` Matthew Garrett
2014-04-14 22:03       ` Oleksandr Natalenko
2014-04-14 22:05         ` Matthew Garrett
2014-04-14 22:08           ` Oleksandr Natalenko

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=1498861.9DHIbmNtA9@spock \
    --to=oleksandr@natalenko.name \
    --cc=mjg59@srcf.ucam.org \
    --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