From: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Subject: Re: [PATCH] staging: iio: add lsm303dlh magnetometer driver
Date: Tue, 17 Apr 2012 11:31:24 +0530 [thread overview]
Message-ID: <20120417060123.GA923@bnru02> (raw)
In-Reply-To: <4F834BE1.2010107@kernel.org>
On Mon, Apr 09, 2012 at 22:51:45 +0200, Jonathan Cameron wrote:
> On 04/09/2012 12:34 PM, Srinidhi KASAGAR wrote:
> > Add support for lsm303dlh magnetometer device.
> >
> > Signed-off-by: srinidhi kasagar <srinidhi.kasagar@stericsson.com>
> > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Hi Srinidhi,
>
> Basically a sound driver with a few easy bits to fix.
>
> Few nitpicks and the error paths in probe need another look.
>
Hi Jonathan,
[...]
>
> We have the old question of _range attributes as well and their
> interaction with scale. I've always been dubious about these,
> mainly because it's not entirely obvious how to format the
> weirder general cases. Do you have a pressing need for range
> or could it just be dropped in favour of allowing write for the
> scale parameter? If nothing else, scale is available for inkernel
> users and range isn't.
If I need to drop range in favor of allowing write access for scale
as you mentioned above, do you mean to implement _write_raw with
IIO_CHAN_INFO_CALIBSCALE abi? Does it mean that user should be able
to pass the scale factors so that driver interprets it to the
corresponding range?
Srinidhi
next prev parent reply other threads:[~2012-04-17 6:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 11:34 [PATCH] staging: iio: add lsm303dlh magnetometer driver Srinidhi KASAGAR
2012-04-09 17:50 ` Linus Walleij
2012-04-09 18:04 ` Jonathan Cameron
2012-04-09 20:51 ` Jonathan Cameron
2012-04-13 11:09 ` Srinidhi Kasagar
2012-04-13 13:55 ` Jonathan Cameron
2012-04-17 6:01 ` Srinidhi Kasagar [this message]
2012-04-17 6:14 ` Jonathan Cameron
2012-04-17 6:29 ` Shubhrajyoti Datta
2012-04-17 6:47 ` Srinidhi Kasagar
2012-04-17 7:22 ` Jonathan Cameron
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=20120417060123.GA923@bnru02 \
--to=srinidhi.kasagar@stericsson.com \
--cc=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).