From: Jonathan Cameron <jic23@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"jacopo@jmondi.org" <jacopo@jmondi.org>
Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Magnus Damm <magnus.damm@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] iio: Add Maxim MAX11100 driver
Date: Sat, 10 Dec 2016 17:54:20 +0000 [thread overview]
Message-ID: <97c5f3f5-3241-b80b-6d0b-22bf28ce9581@kernel.org> (raw)
In-Reply-To: <CAMuHMdWK1ZaqK=-0dw_ZT=fDjHj9jWNUnue+1+NP+rp8Dyps8w@mail.gmail.com>
On 07/12/16 12:22, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> On Wed, Dec 7, 2016 at 9:29 AM, jacopo@jmondi.org <jacopo@jmondi.org> wrote:
>> On 06/12/2016 22:00, Peter Meerwald-Stadler wrote:
>>> On Tue, 6 Dec 2016, Jacopo Mondi wrote:
>>>> Add IIO driver for Maxim MAX11100 single-channel ADC.
>>>> Support raw_read mode only.
>>>
>>> the read_raw() is supposed to return millivolts (after application of
>>> offset and scale); maybe need _SCALE?
>>
>> How can I return millivolts here? They vary in function of the supplied Vref
>> as ( V = val * Vref / (2 ^ 16 - 1)) where "val" is digital value output by
>> the ADC.
>> Since Vref can range from 3.8V to 5.25V, while it's typically 4.096V, isn't
>> it more appropriate to let userspace perform conversion to millivolts, as it
>> knows what Vref value is supplied to the ADC?
>
> Specify Vref in DT?
More specifically specify that it's supplied by a regulator..
If it's a fixed supply then DT should describe it as a fixed regulator.
>
> Which finally gives a good reason to add a DT binding document for
> MAX11100 ;-)
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2016-12-10 17:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 16:30 [PATCH] iio: Add Maxim MAX11100 driver Jacopo Mondi
2016-12-06 21:00 ` Peter Meerwald-Stadler
2016-12-07 8:15 ` Geert Uytterhoeven
2016-12-07 8:29 ` jacopo
2016-12-07 12:22 ` Geert Uytterhoeven
2016-12-10 17:54 ` Jonathan Cameron [this message]
2016-12-10 18:04 ` Jonathan Cameron
2016-12-12 18:11 ` jacopo
2016-12-13 12:37 ` [PATCHv2] iio: adc: " Jacopo Mondi
2016-12-13 13:21 ` Geert Uytterhoeven
2016-12-13 15:53 ` Wolfram Sang
2016-12-30 16:09 ` Jonathan Cameron
2016-12-14 11:54 ` jacopo
2016-12-14 12:14 ` Geert Uytterhoeven
2016-12-13 20:33 ` Peter Meerwald-Stadler
2016-12-14 12:00 ` jacopo
2016-12-30 16:31 ` Jonathan Cameron
2017-01-02 9:19 ` jacopo mondi
2017-01-02 18:02 ` Jonathan Cameron
2016-12-30 16:08 ` Jonathan Cameron
2017-01-02 8:41 ` jacopo mondi
2016-12-30 16:35 ` 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=97c5f3f5-3241-b80b-6d0b-22bf28ce9581@kernel.org \
--to=jic23@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jacopo@jmondi.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=wsa+renesas@sang-engineering.com \
/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).