All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Mardegan <mardy@users.sourceforge.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org,
	"Javier S. Pedro" <maemo@javispedro.com>,
	Ike Panhc <ike.pan@canonical.com>
Subject: Re: Accelerometer and orientation sensor on Lenovo Ideapad S10-3t
Date: Sat, 28 May 2011 10:15:28 +0300	[thread overview]
Message-ID: <4DE0A110.4010102@users.sourceforge.net> (raw)
In-Reply-To: <20110527163346.GD16769@srcf.ucam.org>

On 05/27/2011 07:33 PM, Matthew Garrett wrote:
> If we're not interested in providing continual fine-grained data then 
> the easiest approach may be to present as an input device and then just 
> send updated values whenever you receive the coarse udpate signal. But 
> you probably want to bring this up on LKML so we can make sure 
> everyone's exposing this in the same way.

OK, I will.

>> I know that no one is happy of directly accessing the raw I/O ports, but
>> all my attempts of reading these values through the ACPI interfaces or
>> the EC fields have failed: the fields are always set to 0.
> 
> Does the accelerometer appear as an ACPI device?

No, I think it doesn't. There are some fields in the EC device which
might be related to it, but I tried to read them without luck.
Here's the DSDT, anyway:
http://www.mardy.it/archivos/DSDT.dsl

Ciao,
  Alberto

-- 
http://blog.mardy.it <- geek in un lingua international!

  reply	other threads:[~2011-05-28  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 18:27 Accelerometer and orientation sensor on Lenovo Ideapad S10-3t Alberto Mardegan
2011-05-27 16:33 ` Matthew Garrett
2011-05-28  7:15   ` Alberto Mardegan [this message]
2011-06-08  8:52   ` Anisse Astier
2011-06-08 10:49     ` Alberto Mardegan
2011-05-28 12:03 ` Richard Schütz
2011-06-01  7:23   ` Ike Panhc
2011-06-01 19:29     ` Richard Schütz

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=4DE0A110.4010102@users.sourceforge.net \
    --to=mardy@users.sourceforge.net \
    --cc=ike.pan@canonical.com \
    --cc=maemo@javispedro.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.