From: Anisse Astier <anisse@astier.eu>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Andy Ross <andy.ross@windriver.com>,
Shubhrajyoti <shubhrajyoti@ti.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Corentin Chary <corentincj@iksaif.net>,
linux-input@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/2] input: Pegatron Lucid accelerometer
Date: Fri, 18 Mar 2011 16:39:38 +0100 [thread overview]
Message-ID: <20110318163938.3cb91027@destiny.ordissimo> (raw)
In-Reply-To: <20110131213057.GA9259@srcf.ucam.org>
On Mon, 31 Jan 2011 21:30:57 +0000, Matthew Garrett <mjg59@srcf.ucam.org> wrote :
> On Tue, Jan 18, 2011 at 09:21:31AM -0800, Andy Ross wrote:
>
> > It's just an ACPI method interface, so no dedicated IRQ certainly.
> > The firmware does issue ACPI events on coarse orientation changes
> > (i.e. which edge is up) that we're catching with acpid, so there's no
> > reason this needs to poll all the time in typical usage.
>
> It'd be good to provide those via some more generally-usable mechanism
> than raw ACPI events.
>
Something like that ?
From: Anisse Astier <anisse@astier.eu>
Subject: [PATCH] asus-laptop: Send input event when orientation changes on Pegatron Lucid
Pegatron Lucid tablet sends an ACPI event on coarse orientation changes.
Translate this into KEY_DIRECTION input event.
Signed-off-by: Anisse Astier <anisse@astier.eu>
---
drivers/platform/x86/asus-laptop.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/platform/x86/asus-laptop.c b/drivers/platform/x86/asus-laptop.c
index 75c84f8..d32395c 100644
--- a/drivers/platform/x86/asus-laptop.c
+++ b/drivers/platform/x86/asus-laptop.c
@@ -312,6 +312,8 @@ static const struct key_entry asus_keymap[] = {
{KE_KEY, 0xc4, { KEY_KBDILLUMUP } },
{KE_KEY, 0xc5, { KEY_KBDILLUMDOWN } },
{KE_KEY, 0xb5, { KEY_CALC } },
+ /* Pegatron Lucid tablet specific */
+ {KE_KEY, 0xEA, { KEY_DIRECTION } }, /* Orientation changed */
{KE_END, 0},
};
--
1.7.3.2
next prev parent reply other threads:[~2011-03-18 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:56 [PATCH 0/2] Pegatron Lucid tablet accelerometer Andy Ross
2011-01-17 17:56 ` [PATCH 1/2] input: Pegatron Lucid accelerometer Andy Ross
2011-01-18 5:48 ` Shubhrajyoti
2011-01-18 5:59 ` Dmitry Torokhov
2011-01-18 17:21 ` Andy Ross
[not found] ` <4D35CC1B.3020808-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2011-01-31 21:30 ` Matthew Garrett
2011-03-18 15:39 ` Anisse Astier [this message]
2011-01-17 17:56 ` [PATCH 2/2] asus-laptop: Support pega_accel driver Andy Ross
2011-01-17 18:49 ` [PATCH 0/2] Pegatron Lucid tablet accelerometer Dmitry Torokhov
2011-01-17 22:14 ` Andy Ross
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 20:14 [PATCH 0/3] " Andy Ross
2011-01-14 20:14 ` [PATCH 1/2] input: Pegatron Lucid accelerometer Andy Ross
2011-01-15 16:22 ` Corentin Chary
2011-01-15 22:16 ` Dmitry Torokhov
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=20110318163938.3cb91027@destiny.ordissimo \
--to=anisse@astier.eu \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=andy.ross@windriver.com \
--cc=corentincj@iksaif.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shubhrajyoti@ti.com \
/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