X86 platform drivers
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Javier S. Pedro" <maemo@javispedro.com>
Cc: platform-driver-x86@vger.kernel.org, floe@butterbrot.org
Subject: Re: Looking for some pointers on WMI/EC access
Date: Wed, 1 Dec 2010 20:19:39 +0000	[thread overview]
Message-ID: <20101201201939.GA13106@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTinRS_3vjoWDYVtY3eKbOhFSPDpWJ5YgjGtByDQC@mail.gmail.com>

On Wed, Dec 01, 2010 at 09:13:51PM +0100, Javier S. Pedro wrote:
> 2010/12/1 Matthew Garrett <mjg59@srcf.ucam.org>:
> > Excellent! Send a driver and I'll get it merged.
> 
> Note that I have read the iasl -d'd DSDT myself, so I ponder if that
> forbids me from writing the module (due to unclean room and all that);
> either way, here's the source of the test module I used [1].

We've never really worried about tainting from ACPI - you're writing coe 
that interfaces with that rather than copying any of their code, so it 
should be fine.

> Only available are the front keys -- with the rotation one not being
> fired when not in "tablet mode" (the EC event is not fired, seemingly)
> --  and also "tablet mode" detection, mapped of course to
> SW_TABLET_MODE.
> There's also some kind of orientation detection events that I'm yet to
> fully understand but seem nearly useless. I would very much prefer to
> read the raw accelerometer values from EC or HDAPS.

Ok.

> Also: should this be a separate "lenovo-wmi" driver or integrated with
> lenovo-laptop?

I'd go with lenovo-wmi.

> [1] http://gitorious.org/iaps/lsrot/blobs/master/lsrot.c

Wonderful. I'll take a look.

Thanks!
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-12-01 20:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  0:16 Looking for some pointers on WMI/EC access Javier S. Pedro
2010-12-01  1:31 ` Matthew Garrett
2010-12-01 20:13   ` Javier S. Pedro
2010-12-01 20:19     ` Matthew Garrett [this message]
     [not found] <1271518653.4549.186.camel@flunder>
2010-04-18 19:21 ` Corentin Chary
2010-04-19 14:25   ` Florian Echtler
2010-04-19 15:46     ` Corentin Chary
     [not found]       ` <1271746353.16585.9.camel@flunder>
2010-04-20  7:21         ` Corentin Chary
2010-04-20  7:30           ` Corentin Chary
2010-04-20 11:21             ` Florian Echtler
2010-04-20 12:09               ` Corentin Chary
2010-04-21 12:46                 ` Florian Echtler
2010-04-21 13:33                   ` Matthew Garrett
2010-04-21 14:30                     ` Florian Echtler
2010-04-21 14:32                       ` Matthew Garrett
2010-04-22  8:21                         ` Florian Echtler
2010-04-22 13:36                           ` Matthew Garrett
     [not found]                             ` <1271944219.29664.42.camel@pancake.fritz.box>
2010-04-22 13:53                               ` Matthew Garrett
2010-04-22 14:05                                 ` Matthew Garrett
2010-04-23 11:24                                   ` Florian Echtler
2010-04-23 17:47                                     ` Matthew Garrett
2010-04-22 14:33                                 ` Corentin Chary

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=20101201201939.GA13106@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=floe@butterbrot.org \
    --cc=maemo@javispedro.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