From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Matthew Garrett <mjg@redhat.com>,
Rezwanul Kabir <Rezwanul_Kabir@dell.com>,
Alex Hung <alex.hung@canonical.com>,
Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: Dell Vostro V131 hotkeys revisited
Date: Thu, 2 Jul 2015 22:58:32 +0200 [thread overview]
Message-ID: <201507022258.32104@pali> (raw)
In-Reply-To: <20150702204122.GA2610@eudyptula.hq.kempniu.pl>
[-- Attachment #1: Type: Text/Plain, Size: 2477 bytes --]
On Thursday 02 July 2015 22:41:22 Michał Kępień wrote:
> > Yes, I'm still thinking about some missing init call.
>
> I finally figured it out and we were right - to enable event
> reporting via WMI, a WMI method call with a specially crafted buffer
> passed as an argument is needed. (Though the SMI lead was correct as
> the WMI method generates an SMI calling a BIOS function specified in
> the buffer passed.)
>
Nice :-) Can you write which WMI call needs to be called?
> I'll be happy to prepare a patch, though I'll appreciate some
> guidance in two areas:
>
> 1) The GUID, buffer format and the function to use (DELL_APP_GUID,
> struct app_wmi_args and dell_wmi_perform_query(), respectively)
> are already defined in drivers/leds/dell-led.c. However, the call to
> be made is obviously not related to LEDs, but rather to WMI hotkeys,
> which are handled in drivers/platform/x86/dell-wmi.c. Also, the call
> should only be made on a Vostro V131 and DMI-based filtering is done
> in yet another file, drivers/platform/x86/dell-laptop.c. Where
> should the fix be placed?
>
Last time when I looked into dell-led.c code it called some WMI
functions which are just re-implementation of SMI based SMBIOS
functions. From information which I have that is just WMI interface for
dell SMBIOS one.
I already asked Alex and other people for official ACPI/WMI Dell
documentation, so we would be able to solve these hotkey problems once
and for all, but I did not get anything yet.
What I found on internet is just this one out-of-dated documentation:
http://vpsservice1.sampo.com.tw/sampo_update/document/jimmy/ACPI-WMI%20.pdf
I would suggest you to read it (it is not long) to see Dell WMI methods
are just ACPI "wrapper" around Dell SMBIOS (dcdbas.ko driver) used by
dell-laptop.ko.
> 2) Pressing hotkey #3 on a Dell Vostro V131 generates WMI event
> 0xe025, but no keycode. Apparently, Dell XPS L502X generates the
> same WMI event for a hotkey which also generates a keycode [1].
> What's the best way to solve this conflict?
>
> [1] commit f1566f0: "dell-wmi: Add keys for Dell XPS L502X"
Look at dell-wmi.c source code. Which event format is that? New one
(partially described in above PDF document) when dell_new_hk_type is
true? Or old one?
Can you please enable pr_debug() in dell-wmi.c and send dmesg output
from dell-wmi.ko (specially dell_wmi_notify)?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-07-02 20:58 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 11:26 Dell Vostro V131 hotkeys revisited Michał Kępień
2015-06-23 11:46 ` Pali Rohár
2015-06-23 19:40 ` Michał Kępień
2015-06-23 19:47 ` Pali Rohár
2015-06-24 11:18 ` Michał Kępień
2015-06-24 13:23 ` Pali Rohár
2015-06-25 9:02 ` Michał Kępień
2015-06-27 18:50 ` Pali Rohár
2015-06-30 7:38 ` Michał Kępień
2015-06-30 8:00 ` Pali Rohár
2015-07-01 8:32 ` Michał Kępień
2015-07-01 8:40 ` Pali Rohár
2015-07-01 10:11 ` Michał Kępień
2015-07-01 10:55 ` Pali Rohár
2015-07-02 20:41 ` Michał Kępień
2015-07-02 20:58 ` Pali Rohár [this message]
2015-07-03 6:52 ` Michał Kępień
2015-07-03 7:48 ` Pali Rohár
2015-07-03 11:26 ` Michał Kępień
2015-07-03 11:43 ` Pali Rohár
2015-07-03 13:23 ` Michał Kępień
2015-07-03 13:32 ` Pali Rohár
2015-07-03 13:50 ` Michał Kępień
2015-07-03 14:09 ` Pali Rohár
2015-07-03 14:14 ` Pali Rohár
2015-07-03 18:22 ` Gabriele Mazzotta
2015-07-03 20:07 ` Michał Kępień
2015-07-03 20:30 ` Gabriele Mazzotta
2015-07-04 19:41 ` Pali Rohár
2015-07-04 20:34 ` Gabriele Mazzotta
2015-07-03 20:55 ` Michał Kępień
2015-07-04 19:13 ` Pali Rohár
2015-07-04 19:47 ` Pali Rohár
2015-07-27 19:27 ` Michał Kępień
2015-07-07 18:36 ` Mario Limonciello
2015-07-07 21:01 ` Pali Rohár
2015-07-08 3:21 ` Michał Kępień
2015-07-08 3:53 ` Michał Kępień
2015-07-22 7:35 ` Michał Kępień
2015-08-31 9:51 ` Michał Kępień
2015-09-10 4:38 ` Darren Hart
2015-11-13 10:17 ` Michał Kępień
2015-12-07 11:43 ` Pali Rohár
2015-12-16 9:05 ` Michał Kępień
2015-12-16 9:30 ` Pali Rohár
2015-12-16 10:29 ` Hans de Goede
2015-12-17 8:05 ` Michał Kępień
2015-12-17 9:48 ` Hans de Goede
2015-12-17 18:47 ` Pali Rohár
2015-12-17 18:54 ` Hans de Goede
2015-12-19 0:02 ` Darren Hart
2015-12-19 9:59 ` Pali Rohár
2015-12-18 7:10 ` Michał Kępień
2015-12-18 10:44 ` Hans de Goede
2015-12-19 12:31 ` Michał Kępień
2015-07-04 21:24 ` Pali Rohár
2015-07-05 4:51 ` Michał Kępień
2015-06-23 12:18 ` Pali Rohár
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=201507022258.32104@pali \
--to=pali.rohar@gmail.com \
--cc=Rezwanul_Kabir@dell.com \
--cc=alex.hung@canonical.com \
--cc=dvhart@infradead.org \
--cc=kernel@kempniu.pl \
--cc=mjg@redhat.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