From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
"Palatis Tseng" <palatis@gmail.com>,
"Pavel Machek" <pavel@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] lis3lv02d: add axes knowledge of HP Pavilion dv5 models
Date: Tue, 10 Feb 2009 22:28:58 +0100 [thread overview]
Message-ID: <cb7bb73a0902101328n25f64c9dqd6dabe62b05273ac@mail.gmail.com> (raw)
In-Reply-To: <49917650.1060208@tudelft.nl>
On Tue, Feb 10, 2009 at 1:42 PM, Éric Piel <E.A.B.Piel@tudelft.nl> wrote:
> Can you try something like this in lis3lv02d_poweron():
> adev.read(handle, CTRL_REG2, &val);
> val |= CTRL2_BDU | CTRL2_IEN;
> + val &= ~CTRL2_BLE;
> adev.write(handle, CTRL_REG2, val);
Ok, this is getting crazier and crazier. Apparently, setting the
CTRL2_BLE bit this way makes no difference, and so does setting it
with val |= (i.e. enabling it): in both cases, if I debug
lis3lv02d_read_16 I always get 0 in the lower byte and something in
the upper byte.
By forcefully swapping lo and hi I actually get very little
fluctuations in the Y and Z axes (so small that jstest doesn't detect
them), but I still get huge (4k) fluctuations in the X axis:
apparently, this axis has very small SIGNED fluctuations around the 0,
which translate to fluctuations between 255 and 1
Now, the lo/hi thing might be solved some other way (e.g. by checking
the BLE bit and relying on its setting instead of trying to force it,
and then swapping hi and lo as needed). But how do we solve the
SIGNEDNESS of lo ?
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-02-10 21:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 0:48 Giuseppe Bilotta
2009-02-07 14:47 ` Éric Piel
2009-02-07 23:59 ` Giuseppe Bilotta
2009-02-09 9:47 ` Pavel Machek
2009-02-09 9:53 ` Giuseppe Bilotta
2009-02-09 9:58 ` Pavel Machek
2009-02-09 11:45 ` Giuseppe Bilotta
2009-02-09 13:33 ` Giuseppe Bilotta
2009-02-10 10:10 ` Pavel Machek
2009-02-10 21:39 ` Giuseppe Bilotta
2009-02-10 22:47 ` Éric Piel
2009-02-10 22:48 ` Giuseppe Bilotta
2009-02-10 23:17 ` Andrew Morton
2009-02-10 23:22 ` Éric Piel
2009-02-10 23:17 ` Éric Piel
2009-02-10 23:34 ` Éric Piel
[not found] ` <498E46F2.1020401@gmail.com>
2009-02-09 23:37 ` Éric Piel
[not found] ` <4990DEFD.4010700@gmail.com>
2009-02-10 10:34 ` Éric Piel
2009-02-10 11:07 ` Giuseppe Bilotta
2009-02-10 12:42 ` Éric Piel
2009-02-10 20:29 ` Giuseppe Bilotta
2009-02-10 20:31 ` Giuseppe Bilotta
2009-02-10 21:28 ` Giuseppe Bilotta [this message]
2009-02-10 21:33 ` Giuseppe Bilotta
2009-02-09 9:44 ` Pavel Machek
2009-02-09 9:50 ` Giuseppe Bilotta
[not found] ` <1234191743.3156.2.camel@localhost.localdomain>
2009-02-09 16:50 ` Giuseppe Bilotta
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=cb7bb73a0902101328n25f64c9dqd6dabe62b05273ac@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=E.A.B.Piel@tudelft.nl \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=palatis@gmail.com \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®