From: Colin Ian King <colin.king@canonical.com>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: platform-driver-x86@vger.kernel.org,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] dell: add new dell WMI format for the AIO machines
Date: Thu, 07 Mar 2013 10:17:43 +0000 [thread overview]
Message-ID: <51386947.1070406@canonical.com> (raw)
In-Reply-To: <1362624492-19193-1-git-send-email-acelan.kao@canonical.com>
On 07/03/13 02:48, AceLan Kao wrote:
> There is a new DELL WMI spec. with new WMI event format.
> I'm working on the AIO machines, but I think the new format will apply to
> all the Dell's machines, not only for AIO, which will be released later
> this year.
>
> The new format of the WMI buffer is shown as below
> word 0 - the number of words following in the WMI buffer(not including
> this word.
> word 1 - the event type
> 0x0000 - A hot key is pressed or an event occurred
> 0x000F - A sequence of hot keys are pressed
> word 2 and on - the event data
>
> Signed-off-by: AceLan Kao <acelan.kao@canonical.com>
> ---
> drivers/platform/x86/dell-wmi-aio.c | 51 +++++++++++++++++++++++++++++++++----
> 1 file changed, 46 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/platform/x86/dell-wmi-aio.c b/drivers/platform/x86/dell-wmi-aio.c
> index 3f94545..bf8fc53 100644
> --- a/drivers/platform/x86/dell-wmi-aio.c
> +++ b/drivers/platform/x86/dell-wmi-aio.c
> @@ -34,6 +34,14 @@ MODULE_LICENSE("GPL");
> #define EVENT_GUID1 "284A0E6B-380E-472A-921F-E52786257FB4"
> #define EVENT_GUID2 "02314822-307C-4F66-BF0E-48AEAEB26CC8"
>
> +struct dell_wmi_event {
> + u16 length;
> + /* 0x000: A hot key pressed or an event occurred
> + * 0x00F: A sequence of hot keys are pressed */
> + u16 type;
> + u16 event[];
> +};
> +
> static const char *dell_wmi_aio_guids[] = {
> EVENT_GUID1,
> EVENT_GUID2,
> @@ -46,11 +54,36 @@ MODULE_ALIAS("wmi:"EVENT_GUID2);
> static const struct key_entry dell_wmi_aio_keymap[] = {
> { KE_KEY, 0xc0, { KEY_VOLUMEUP } },
> { KE_KEY, 0xc1, { KEY_VOLUMEDOWN } },
> + { KE_KEY, 0xe030, { KEY_VOLUMEUP } },
> + { KE_KEY, 0xe02e, { KEY_VOLUMEDOWN } },
> + { KE_KEY, 0xe020, { KEY_MUTE } },
> + { KE_KEY, 0xe027, { KEY_DISPLAYTOGGLE } },
> + { KE_KEY, 0xe006, { KEY_BRIGHTNESSUP } },
> + { KE_KEY, 0xe005, { KEY_BRIGHTNESSDOWN } },
> + { KE_KEY, 0xe00b, { KEY_SWITCHVIDEOMODE } },
> { KE_END, 0 }
> };
>
> static struct input_dev *dell_wmi_aio_input_dev;
>
> +/*
> + * The new WMI event data format will follow the dell_wmi_event structure
> + * So, we will check if the buffer matches the format
> + */
> +static bool dell_wmi_aio_event_check(u8 *buffer)
> +{
> + dell_wmi_event *event = (dell_wmi_event *)buffer;
> +
> + if (event == NULL)
> + return false;
I did mention in my last message that we need to also check that the
buffer length needs checking. Suppose it is just 1 byte long (which it
may be in the original Dell AIO case or in the future) - access to
fields in event will be outside this buffer.
So you need to ensure that obj->buffer.length is at least 6 to be able
to reference event->length, event->type and event[0].
> +
> + if ((event->type == 0 || event->type == 0xf) &&
> + event->length >= 2)
> + return true;
> +
> + return false;
> +}
> +
> static void dell_wmi_aio_notify(u32 value, void *context)
> {
> struct acpi_buffer response = { ACPI_ALLOCATE_BUFFER, NULL };
> @@ -65,7 +98,7 @@ static void dell_wmi_aio_notify(u32 value, void *context)
>
> obj = (union acpi_object *)response.pointer;
> if (obj) {
> - unsigned int scancode;
> + unsigned int scancode = 0;
>
> switch (obj->type) {
> case ACPI_TYPE_INTEGER:
> @@ -75,13 +108,21 @@ static void dell_wmi_aio_notify(u32 value, void *context)
> scancode, 1, true);
> break;
> case ACPI_TYPE_BUFFER:
> - /* Broken machines return the scancode in a buffer */
> - if (obj->buffer.pointer && obj->buffer.length > 0) {
> - scancode = obj->buffer.pointer[0];
> + if (dell_wmi_aio_event_check(obj->buffer.pointer)) {
> + dell_wmi_event *event =
> + (dell_wmi_event *)obj->buffer.pointer;
> + scancode = event->event[0];
> + } else {
> + /* Broken machines return the scancode in a
> + buffer */
> + if (obj->buffer.pointer &&
> + obj->buffer.length > 0)
> + scancode = obj->buffer.pointer[0];
> + }
> + if (scancode)
> sparse_keymap_report_event(
> dell_wmi_aio_input_dev,
> scancode, 1, true);
> - }
> break;
> }
> }
>
next prev parent reply other threads:[~2013-03-07 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 2:48 [PATCH] dell: add new dell WMI format for the AIO machines AceLan Kao
2013-03-07 10:17 ` Colin Ian King [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-08 7:44 AceLan Kao
2013-03-08 7:50 ` Matthew Garrett
2013-03-08 8:19 ` AceLan Kao
2013-03-08 10:40 ` Colin Ian King
2013-03-06 7:51 AceLan Kao
2013-03-06 8:33 ` Colin Ian King
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=51386947.1070406@canonical.com \
--to=colin.king@canonical.com \
--cc=acelan.kao@canonical.com \
--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 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.