From: Lars-Peter Clausen <lars@metafoo.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Hector Palacios <hector.palacios@digi.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Marek Vasut <marex@denx.de>,
"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>
Subject: Re: Accessing specific hardware features of mxs-lradc
Date: Tue, 02 Jul 2013 17:55:29 +0200 [thread overview]
Message-ID: <51D2F7F1.7000305@metafoo.de> (raw)
In-Reply-To: <51D2F580.5070205@free-electrons.com>
On 07/02/2013 05:45 PM, Alexandre Belloni wrote:
> On 02/07/2013 17:21, Lars-Peter Clausen wrote:
>>>>
>>>> I was looking at that yesterday as I had to had a scale for the
>>>> temperature sensors. You'll have to be careful because the maximum
>>>> measured voltage when DIVIDE_BY_TWO is not set is 1.85V and when it is
>>>> set, it becomes VDDIO - 50mv.
>>
>> I had a quick peak at the datasheet and I think that's a typo. VDDIO is 3.3V.
>> This sentence also doesn't make much sense if divide by two would actually
>> lower the range. "For input channels (other than BATT, 5V, or VDDIO) with
>> signals larger than 1.85 V, the divide-by-two option should be set."
>>
>
> Yeah, what I think they meant is if !DIVIDE_BY_TWO : Vmax = 1.85V else
> Vmax = 3.25V. So it may not be as easy as multiplying hte scale by two.
> I couldn't test it, so I didn't implement it.
Parse error on my side, in the datasheet it is a hyphen not a minus, so I
though the sentence meant that the maximum is 50mV.
I guess it is still a divide by two, but since the max input voltage is 3.3V
you simply can't max out the ADC anymore since the maximum value corresponds to
3.7V
-Lars
prev parent reply other threads:[~2013-07-02 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:49 Accessing specific hardware features of mxs-lradc Hector Palacios
2013-07-02 12:06 ` Marek Vasut
2013-07-02 12:58 ` Lars-Peter Clausen
2013-07-02 13:28 ` Alexandre Belloni
2013-07-02 14:55 ` Hector Palacios
2013-07-02 15:21 ` Lars-Peter Clausen
2013-07-02 15:41 ` Lars-Peter Clausen
2013-07-02 15:45 ` Alexandre Belloni
2013-07-02 15:55 ` Lars-Peter Clausen [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=51D2F7F1.7000305@metafoo.de \
--to=lars@metafoo.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=fabio.estevam@freescale.com \
--cc=hector.palacios@digi.com \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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.