From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX28 die temperature
Date: Tue, 23 Oct 2012 12:32:37 +0200 [thread overview]
Message-ID: <201210231232.37469.marex@denx.de> (raw)
In-Reply-To: <81D7F19D-A9F8-4022-81F0-B8A836F7F087@turczak.de>
Dear Peter Turczak,
> Hi Marek,
>
> On Oct 23, 2012, at 10:52 AM, Marek Vasut wrote:
> > We have some basic LRADC driver in upstream already, you should use that.
> >
> > See drivers/staging/iio/adc/mxs-lradc.c
>
> Thanks for the heads-up.
> I was referring to this driver (pulled from linus' 3.7rc), it does not
> currently seem to have a consumer api for use within other kernel modules.
> Maybe I'm just heading the wrong way now...
Ah yes, it doesn't ... feel free to implement it. It can -- though -- read the
CPU die temperature, just sample those two channels, substract one from another
and multiply by the coeficient ... you'll find that in the datasheet.
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-10-23 10:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 15:13 i.MX28 die temperature Randle, Bill
2012-03-29 2:37 ` Shawn Guo
2012-03-29 15:52 ` Randle, Bill
2012-04-04 23:51 ` Marek Vasut
2012-04-05 0:07 ` Randle, Bill
2012-04-05 0:36 ` Fabio Estevam
2012-06-22 11:49 ` Juergen Beisert
2012-06-22 17:19 ` Marek Vasut
2012-06-26 8:12 ` Juergen Beisert
2012-06-26 19:02 ` Marek Vasut
2012-06-27 7:21 ` Jonathan Cameron
2012-06-27 12:00 ` Marek Vasut
2012-06-27 12:06 ` Jonathan Cameron
2012-06-27 12:25 ` Marek Vasut
2012-06-27 12:33 ` Juergen Beisert
2012-06-27 22:58 ` Marek Vasut
2012-06-28 8:00 ` Jonathan Cameron
2012-06-28 3:05 ` Marek Vasut
2012-06-28 15:42 ` Marek Vasut
2012-10-23 8:48 ` Peter Turczak
2012-10-23 8:52 ` Marek Vasut
2012-10-23 10:22 ` Peter Turczak
2012-10-23 10:32 ` Marek Vasut [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=201210231232.37469.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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).