From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, eric.piel@tremplin-utc.net, pavel@suse.cz
Subject: Re: [PATCHv7] lis3lv02d: support both one- and two-byte sensors
Date: Wed, 11 Feb 2009 23:44:20 +0100 [thread overview]
Message-ID: <cb7bb73a0902111444h46be9b65pa01d4b2b9c31afe8@mail.gmail.com> (raw)
In-Reply-To: <20090211143844.27ca0d6c.akpm@linux-foundation.org>
On Wed, Feb 11, 2009 at 11:38 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Wed, 11 Feb 2009 11:06:43 +0100
> Giuseppe Bilotta <giuseppe.bilotta@gmail.com> wrote:
>
>> Sensors responding with 0x3B to WHO_AM_I only have one data register per
>> direction, thus returning a signed byte from the position which is
>> occupied by the MSB in sensors responding with 0x3A.
>>
>> Since multiple sensors share the reply to WHO_AM_I, we rename the
>> defines to better indicate what they identify (family of single and
>> double precision sensors).
>>
>> We support both kind of sensors by checking for the sensor type on init
>> and defining appropriate data-access routines and sensor limits (for the
>> joystick) depending on what we find.
>>
>
> Which tree is this patch against?
>
>> --- a/drivers/hwmon/lis3lv02d.c
>> +++ b/drivers/hwmon/lis3lv02d.c
>> @@ -53,9 +53,6 @@
>> * joystick.
>> */
>>
>> -/* Maximum value our axis may get for the input device (signed 12 bits) */
>> -#define MDPS_MAX_VAL 2048
>> -
>> struct acpi_lis3lv02d adev = {
>> .misc_wait = __WAIT_QUEUE_HEAD_INITIALIZER(adev.misc_wait),
>> };
>
> Current Linus mainline has
>
> struct acpi_lis3lv02d adev;
> EXPORT_SYMBOL_GPL(adev);
>
> here.
I based my patch on Linus' tree, plus Pavel's patch which I've been
told is on your tree.
Is your tree available for git? I can try basing it on yours directly.
> Also, this comment:
>
> /*
> * The sensor can also generate interrupts (DRDY) but it's pretty pointless
> * because their are generated even if the data do not change. So it's better
> * to keep the interrupt for the free-fall event. The values are updated at
> * 40Hz (at the lowest frequency), but as it can be pretty time consuming on
> * some low processor, we poll the sensor only at 20Hz... enough for the
> * joystick.
> */
>
> seems to be describing something which isn't there.
I have no idea about that, I didn't touch it at all.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-02-11 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 1:04 [PATCHv6] " Giuseppe Bilotta
2009-02-11 9:47 ` Éric Piel
2009-02-11 10:06 ` [PATCHv7] " Giuseppe Bilotta
2009-02-11 10:17 ` Éric Piel
2009-02-11 22:38 ` Andrew Morton
2009-02-11 22:44 ` Giuseppe Bilotta [this message]
2009-02-11 22:53 ` Andrew Morton
2009-02-11 23:06 ` Giuseppe Bilotta
2009-02-11 23:27 ` Andrew Morton
2009-02-11 23:53 ` Éric Piel
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=cb7bb73a0902111444h46be9b65pa01d4b2b9c31afe8@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--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®