From: Lars-Peter Clausen <lars@metafoo.de>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Jonathan Cameron <jic23@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: mxs-lradc: compute temperature from channel 8 and 9
Date: Tue, 19 Nov 2013 12:31:35 +0100 [thread overview]
Message-ID: <528B4C17.60001@metafoo.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1311191149130.18664@pmeerw.net>
On 11/19/2013 11:51 AM, Peter Meerwald wrote:
>
>> The mxs LRADC is able to read an internal die temperature sensor. The
>> temperature has to be calculated from the value read on channel 8 and channel 9.
>> To be able to expose the result to hwmon, implement iio channel 8 as
>> (channel 9 - channel 8). Then, implement IIO_CHAN_INFO_SCALE and
>> IIO_CHAN_INFO_OFFSET so that it can be processed by hwmon through the in kernel
>> provider/consumer mechanism.
>
> wouldn't IIO_CHAN_INFO_PROCESSED be more suitable than IIO_CHAN_INFO_RAW?
No. PROCESSED means it has the right scale and offset. This is still a raw
value.
- Lars
WARNING: multiple messages have this Message-ID (diff)
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iio: mxs-lradc: compute temperature from channel 8 and 9
Date: Tue, 19 Nov 2013 12:31:35 +0100 [thread overview]
Message-ID: <528B4C17.60001@metafoo.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1311191149130.18664@pmeerw.net>
On 11/19/2013 11:51 AM, Peter Meerwald wrote:
>
>> The mxs LRADC is able to read an internal die temperature sensor. The
>> temperature has to be calculated from the value read on channel 8 and channel 9.
>> To be able to expose the result to hwmon, implement iio channel 8 as
>> (channel 9 - channel 8). Then, implement IIO_CHAN_INFO_SCALE and
>> IIO_CHAN_INFO_OFFSET so that it can be processed by hwmon through the in kernel
>> provider/consumer mechanism.
>
> wouldn't IIO_CHAN_INFO_PROCESSED be more suitable than IIO_CHAN_INFO_RAW?
No. PROCESSED means it has the right scale and offset. This is still a raw
value.
- Lars
next prev parent reply other threads:[~2013-11-19 11:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 10:36 [PATCH] iio: mxs-lradc: compute temperature from channel 8 and 9 Maxime Ripard
2013-11-19 10:36 ` Maxime Ripard
2013-11-19 10:51 ` Peter Meerwald
2013-11-19 10:51 ` Peter Meerwald
2013-11-19 11:31 ` Lars-Peter Clausen [this message]
2013-11-19 11:31 ` Lars-Peter Clausen
2013-11-30 12:15 ` Jonathan Cameron
2013-11-30 12:15 ` Jonathan Cameron
2013-11-30 12:19 ` Jonathan Cameron
2013-11-30 12:19 ` Jonathan Cameron
2013-11-30 12:24 ` Michał Mirosław
2013-11-30 12:24 ` Michał Mirosław
2013-11-30 12:27 ` Jonathan Cameron
2013-11-30 12:27 ` Jonathan Cameron
2013-11-30 12:29 ` Jonathan Cameron
2013-11-30 12:29 ` Jonathan Cameron
2013-11-30 13:37 ` Maxime Ripard
2013-11-30 13:37 ` Maxime Ripard
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=528B4C17.60001@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=pmeerw@pmeerw.net \
/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.