From: Bhuvanchandra <bhuvanchandra.dv@toradex.com>
To: Stefan Agner <stefan@agner.ch>
Cc: <linux-iio@vger.kernel.org>, <jic23@kernel.org>,
<maitysanchayan@gmail.com>, <B38611@freescale.com>,
<knaack.h@gmx.de>, <lars@metafoo.de>, <pmeerw@pmeerw.net>,
<shawn.guo@linaro.org>, <linux-kernel@vger.kernel.org>,
<bhuvanchandra.dv@toradex.com>
Subject: Re: [PATCH] vf610_adc: Fix internal temperature calculation
Date: Tue, 13 Oct 2015 09:07:55 +0530 [thread overview]
Message-ID: <561C7C93.4090608@toradex.com> (raw)
In-Reply-To: <0b977c21c414aef0c250755c9d772ead@agner.ch>
Hi Stefan,
Sorry! for the delay.
On 10/08/2015 11:46 AM, Stefan Agner wrote:
> Hi Bhuvan,
>
> On 2015-09-23 06:43, Bhuvanchandra DV wrote:
>> There is an observed temperature difference of ~20°C with the
>> internal temperature reading and the temperature measured on
>> SoC package. Existing calculations consider the typical values
>> provided in datasheet. Those typical values are valid for
>> VREFH_ADC at 3.0V. Voltage at 25°C is different for different
>> VREFH_ADC voltages. With VREFH_ADC at 3.3V, voltage at 25°C is
>> 0.699V. Hence update the VTEMP25 to 0.699V which gives ADCR@Temp25
>> as 867 and the final temperature readings differs with ~5°C from
>> the external readings.
> I am not entirely happy with the message. The proposed changes seem not
> to alter the offset which would explain a ~20°C difference... Where do
> this 20°C come from?
The ~20°C difference is observed at higher temperatures when VTEMP25
at VREDH_ADC of 3V0 is considered. Will update the comment according
to the updated VTEMP25 constant instead of the 20°C difference which
is confusing wrt the changes done here.
Best regards,
Bhuvan
> --
> Stefan
>
>> Formula for finding ADCR@Temp25:
>> ADCR@Temp25 = (ADCR@Vdd * V@TEMP25 * 10) / VDDconv
>>
>> ADCR@Vdd for 12-Bit ADC = 4095
>> VDDconv = VREFH_ADC * 10
>>
>> VREFH_ADC@3.3V
>> ADCR@Temp25 = (4095 * .699 * 10) / 33
>> ADCR@Temp25 ~= 867
>>
>> | VREFH_ADC | V@TEMP25 | VDDconv | ADCR@Temp25 |
>> | 3.0V | 0.696mV | 30 | 950 |
>> | 3.3V | 0.699mV | 33 | 867 |
>>
>> Signed-off-by: Bhuvanchandra DV<bhuvanchandra.dv@toradex.com>
>> ---
>> drivers/iio/adc/vf610_adc.c | 19 ++++++++++++++-----
>> 1 file changed, 14 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/iio/adc/vf610_adc.c b/drivers/iio/adc/vf610_adc.c
>> index f4df2a7..e7abc13 100644
>> --- a/drivers/iio/adc/vf610_adc.c
>> +++ b/drivers/iio/adc/vf610_adc.c
>> @@ -103,6 +103,13 @@
>>
>> #define DEFAULT_SAMPLE_TIME 1000
>>
>> +/* V at 25°C of 696 mV */
>> +#define VF610_VTEMP25_3V0 950
>> +/* V at 25°C of 699 mV */
>> +#define VF610_VTEMP25_3V3 867
>> +/* Typical sensor slope coefficient at all temperatures */
>> +#define VF610_TEMP_SLOPE_COEFF 1840
>> +
>> enum clk_sel {
>> VF610_ADCIOC_BUSCLK_SET,
>> VF610_ADCIOC_ALTCLK_SET,
>> @@ -636,11 +643,13 @@ static int vf610_read_raw(struct iio_dev *indio_dev,
>> break;
>> case IIO_TEMP:
>> /*
>> - * Calculate in degree Celsius times 1000
>> - * Using sensor slope of 1.84 mV/°C and
>> - * V at 25°C of 696 mV
>> - */
>> - *val = 25000 - ((int)info->value - 864) * 1000000 / 1840;
>> + * Calculate in degree Celsius times 1000
>> + * Using the typical sensor slope of 1.84 mV/°C
>> + * and VREFH_ADC at 3.3V, V at 25°C of 699 mV
>> + */
>> + *val = 25000 - ((int)info->value - VF610_VTEMP25_3V3) *
>> + 1000000 / VF610_TEMP_SLOPE_COEFF;
>> +
>> break;
>> default:
>> mutex_unlock(&indio_dev->mlock);
prev parent reply other threads:[~2015-10-13 3:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 13:43 [PATCH] vf610_adc: Fix internal temperature calculation Bhuvanchandra DV
2015-09-27 15:53 ` Jonathan Cameron
2015-09-29 4:52 ` Bhuvanchandra
2015-10-08 2:01 ` Duan Andy
2015-10-08 2:01 ` Duan Andy
2015-10-11 14:05 ` Jonathan Cameron
2015-10-11 14:07 ` Jonathan Cameron
2015-10-08 6:16 ` Stefan Agner
2015-10-13 3:37 ` Bhuvanchandra [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=561C7C93.4090608@toradex.com \
--to=bhuvanchandra.dv@toradex.com \
--cc=B38611@freescale.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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.