X86 platform drivers
 help / color / mirror / Atom feed
From: Peter Meiser <meiser@gmx-topmail.de>
To: platform-driver-x86@vger.kernel.org
Subject: Re: Dell Vostro V131: special hotkey not working
Date: Sat, 20 Jul 2013 07:03:03 +0200	[thread overview]
Message-ID: <51EA1A07.10105@gmx-topmail.de> (raw)
In-Reply-To: <50FA77C0.4060808@gmx-topmail.de>

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

Hi again,

I found a solution for the 1st issue. It needs a udev quirk to force_release. Please find attached a patch against current udev in Ubuntu 12.04.

For the 2nd issue, I still can't find a way to generate a keycode.

Thanks for your help!
Best regards,
Peter

Am 19.01.2013 11:38, schrieb Peter Meiser:
> Hi Matthew,
> 
> this topic is still valid. Could you help me debugging the hotkeys?
> 
> There're two issues:
> 1. The "Dell support center" hotkey generates keycode 0xEE, but this is done forever. That means that I don't see a release event.
> 2. The "Dell instant launch manager" hotkey doesn't generate anything.
> 
> Thanks a lot in advance,
> Peter
> 
> Am 25.04.2012 16:22, schrieb Matthew Garrett:
>> On Wed, Apr 25, 2012 at 04:19:51PM +0200, Peter Meiser wrote:
>>> Hello Matthew,
>>>
>>> Am 25.04.2012 15:53, schrieb Matthew Garrett:
>>>> watch -n 0.1 cat /proc/interrupts
>>>
>>> When running "watch -n 0,1 cat /proc/interrupts" (watch -n 0.1 errors out, maybe because of German environment???), the following row increases after each press:
>>>
>>>   9:          5          0          0          0   IO-APIC-fasteoi   acpi
>>
>> Ok, so it's definitely being handled by ACPI somehow - probably via WMI, 
>> but unsure. Rez, any chance you can look at the original message and let 
>> us know if this is expected to work with the current driver?
>>

[-- Attachment #2: udev-keymaps-dell.patch --]
[-- Type: text/x-patch, Size: 1616 bytes --]

--- a/extras/keymap/keymaps/dell
+++ b/extras/keymap/keymaps/dell
@@ -25,5 +25,6 @@
 0xA2 playpause # Front panel play/pause
 0xA4 stopcd # Front panel stop
 0xED media # MediaDirect button
+0xEE screenlock # FIXME: Dell Support Center button
 0xD8 screenlock # FIXME: Tablet lock button
 0xD9 f21 # touchpad toggle
diff -Naur a/extras/keymap/95-keyboard-force-release.rules b/extras/keymap/95-keyboard-force-release.rules
--- a/extras/keymap/95-keyboard-force-release.rules	2013-07-20 06:59:13.626208521 +0200
+++ b/extras/keymap/95-keyboard-force-release.rules	2013-07-20 07:00:30.166211692 +0200
@@ -24,6 +24,7 @@
 ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="Studio 1557|Studio 1558", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
 ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="*Latitude*|*Precision*", RUN+="keyboard-force-release.sh $devpath dell-touchpad"
 ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="XPS*", RUN+="keyboard-force-release.sh $devpath dell-xps"
+ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="*Vostro*", RUN+="keyboard-force-release.sh $devpath dell-vostro"
 
 ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO*", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
 
diff -Naur a/extras/keymap/force-release-maps/dell-vostro b/extras/keymap/force-release-maps/dell-vostro
--- a/extras/keymap/force-release-maps/dell-vostro	1970-01-01 01:00:00.000000000 +0100
+++ b/extras/keymap/force-release-maps/dell-vostro	2013-07-20 06:59:45.086209823 +0200
@@ -0,0 +1 @@
+0xEE # Dell Support Center button

  reply	other threads:[~2013-07-20  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F97FA4C.9040201@gmx-topmail.de>
2012-04-25 13:53 ` Dell Vostro V131: special hotkey not working Matthew Garrett
2012-04-25 14:19   ` Peter Meiser
2012-04-25 14:22     ` Matthew Garrett
2012-05-11  5:28       ` Peter Meiser
2013-01-19 10:38       ` Peter Meiser
2013-07-20  5:03         ` Peter Meiser [this message]
2014-06-12  6:58           ` Peter Meiser

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=51EA1A07.10105@gmx-topmail.de \
    --to=meiser@gmx-topmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox