All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Éric Piel" <eric.piel@tremplin-utc.net>
To: Oliver Neukum <oliver@neukum.org>
Cc: Pavel Machek <pavel@suse.cz>, Jiri Kosina <jkosina@suse.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Trivial patch monkey <trivial@kernel.org>
Subject: Re: lis3: fix documentation to fit into 80 columns
Date: Tue, 20 Jan 2009 12:02:11 +0100	[thread overview]
Message-ID: <4975AF33.8040101@tremplin-utc.net> (raw)
In-Reply-To: <200901201118.05165.oliver@neukum.org>

Oliver Neukum schreef:
> Am Tuesday 20 January 2009 11:13:49 schrieb Pavel Machek:
>>>>  Sysfs attributes under /sys/devices/platform/lis3lv02d/:
>>>>  position - 3D position that the accelerometer reports. Format: "(x,y,z)"
>>>> -calibrate - read: values (x, y, z) that are used as the base for input class device operation.
>>>> -            write: forces the base to be recalibrated with the current position.
> 
> So you are computing a position according acceleration readings?
Not really, the "position" is actually only the current acceleration
read from the sensor minus the calibration vector. It's more wording
problem, nothing fancy like double integration ;-)

> Isn't that common code to all accelerometers and should be put
> into a higher level?
Nevertheless, this remark is still valid, there are various code that
all the accelerometer drivers could share. I'm thinking in particular of
the sysfs interface, and joystick interface. There has been some work in
this direction with the "industrialio" subsystem. So for now I'm in
"wait and see" mode about this :-)

See you,
Eric

      reply	other threads:[~2009-01-20 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 17:20 lis3: fix documentation to fit into 80 columns Pavel Machek
2009-01-19 23:29 ` Jiri Kosina
2009-01-20 10:13   ` Pavel Machek
2009-01-20 10:16     ` Jiri Kosina
2009-01-20 10:18     ` Oliver Neukum
2009-01-20 11:02       ` Éric Piel [this message]

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=4975AF33.8040101@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=akpm@osdl.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=pavel@suse.cz \
    --cc=trivial@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.