From: Hector Palacios <hector.palacios-i7dp0qKlBMg@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: "linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
"fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org"
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
Subject: Reference voltages for ADC channels
Date: Mon, 8 Jul 2013 08:13:30 +0200 [thread overview]
Message-ID: <51DA588A.5050609@digi.com> (raw)
Greetings,
The other day at linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org we discussed the possibility of having ADC
channels voltage references moved to the DT [1].
In Freescale's i.MX28 and i.MX23, at least, the CPU has 16 ADC channels some of which
are dedicated to measure internal stuff, like CPU temperature and voltages. Some
channels have different fixed divisors and so different reference voltages.
These reference voltages (in mV) are needed to calculate the scale to show through the
sysfs IIO interface, so that a user can easily compute the real measured voltage out
of the sampled data.
The proposed DT entry also appears at [1].
We would love to here opinions about it.
[1] http://www.spinics.net/lists/linux-iio/msg08973.html
Best regards,
--
Hector Palacios
next reply other threads:[~2013-07-08 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 6:13 Hector Palacios [this message]
[not found] ` <51DA588A.5050609-i7dp0qKlBMg@public.gmane.org>
2013-07-12 13:14 ` Reference voltages for ADC channels Hector Palacios
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=51DA588A.5050609@digi.com \
--to=hector.palacios-i7dp0qklbmg@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marex-ynQEQJNshbs@public.gmane.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).