From: "Éric Piel" <eric.piel@tremplin-utc.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [RFC PATCH 09/10] lis3: Scale output values to mg
Date: Tue, 03 Nov 2009 13:25:18 +0000 [thread overview]
Message-ID: <4AF02F3E.7030309@tremplin-utc.net> (raw)
In-Reply-To: <1257250185-7929-10-git-send-email-samu.p.onkalo@nokia.com>
Op 03-11-09 13:32, Daniel Mack schreef:
> On Tue, Nov 03, 2009 at 01:30:07PM +0100, samu.p.onkalo@nokia.com wrote:
>>> On Tue, Nov 03, 2009 at 02:09:44PM +0200, Samu Onkalo wrote:
>>>> Report output values as 1/1000 of earth gravity.
>>> Without having tried that, I assume that changes the values
>>> for all events reported? That would break all userspace
>>> clients of this device, right?
>>>
>> Yes. That is one thing which need to agreed here. One possibility is to
>> implement this as a configurable feature for example using platform data.
>> In that kind of solution default value must be the old way.
>
> Yes please :)
>
Hello,
Actually we had already briefly discussed this with Samu. And I had
given my green light because:
* I don't know any userspace program which would be affected by this
change (they only rely on the relative difference). Arguably, I know
only few programs.
* Eventually, we should converge to a userspace API compatible with any
accelerometer device and exposed by all the accelerometer drivers. So
for now I consider the userspace interface of the lis3 driver quite
"soft", and any move toward this goal good.
* Having platform data to select between old unit/new unit will add
complexity to the driver, which should be avoided whenever possible.
Of course, if you come and tell me that you know some userspace programs
which will be affected by this change, this blows away the first point.
Then I'd be much more willing to have a configurable option. But be
aware that these programs would then blow away themselves if, for
example, they expect a LIS302DL and the actual sensor is a LIS3LV02DL.
So simply fixing these programs and moving to mG might be a better option.
See you,
Eric
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-11-03 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 12:09 [lm-sensors] [RFC PATCH 09/10] lis3: Scale output values to mg Samu Onkalo
2009-11-03 12:17 ` Daniel Mack
2009-11-03 12:30 ` samu.p.onkalo
2009-11-03 12:32 ` Daniel Mack
2009-11-03 13:25 ` Éric Piel [this message]
2009-11-06 11:55 ` samu.p.onkalo
2009-11-10 12:47 ` Daniel Mack
2009-11-10 13:23 ` Éric Piel
2009-11-10 13:31 ` Daniel Mack
2009-11-10 13:42 ` Éric Piel
2009-11-11 7:32 ` Onkalo Samu
2010-04-21 12:10 ` Daniel Mack
2010-04-22 6:33 ` samu.p.onkalo
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=4AF02F3E.7030309@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=lm-sensors@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.