From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: linux-acpi@vger.kernel.org, driverdev-devel@linuxdriverproject.org
Subject: [RFC] [HELP] [WMI] Media keys on MSI GE60 (patching msi_wmi for it)
Date: Fri, 04 Jul 2014 15:05:48 +0700 [thread overview]
Message-ID: <1578502.VNsf8Sat2f@note> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]
Hi there!
I'm trying to modify msi_wmi driver to get it work with mediakeys on my MSI
GE60 laptop.
By default, I get "Unknown event received" message.
For now, I diagnosed that event, that every key press produces has 0x03 (
ACPI_TYPE_BUFFER?) type, instead of 0x01 (ACPI_TYPE_INTEGER) which in-kernel
msi_wmi module wants.
Further diagnostic with that code:
232 › } else if (obj && obj->type == ACPI_TYPE_BUFFER) {
233 › › int eventcode = obj->integer.value;
234 › › pr_info("Eventcode: 0x%x\n", eventcode);
235 › › key = sparse_keymap_entry_from_scancode(msi_wmi_input_dev,
236 › › › › eventcode);
237 › › if (!key) {
238 › › › pr_info("Unknown key pressed - %x\n", eventcode);
239 › › › goto msi_wmi_notify_exit;
240 › › }
241
242 › › pr_info("%d\n",key->type);
243 › } else
244 › › pr_info("Unknown event received\n");
(only patched part)
Gives me following info:
Wen I press on any of media-keys — I get the same eventcode (and every time I
get if(!key) error. Moreover, evencode value changes in time (something about
4 seconds), so, if I'll press some key many times, eventcode value will be
changed after 4s, but it will not change if I press another mediakeys.
Can anybody advice me, why can I experience such behaviour?
And is it a way to get mediakeys working without patching DSDT (last time I
did that I brake my bluetooth module in that way, that even rfkill was unable
to enable it :P)?
--
Best regsrds,
mva
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
reply other threads:[~2014-07-04 8:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1578502.VNsf8Sat2f@note \
--to=mva@mva.name \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=linux-acpi@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.