From: linux@roeck-us•net (Guenter Roeck)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/3] hwmon: Driver for OMAP3 temperature sensor
Date: Sun, 18 Jan 2015 14:18:24 -0800 [thread overview]
Message-ID: <54BC3130.4010401@roeck-us.net> (raw)
In-Reply-To: <20150118203346.GA29863@amd>
On 01/18/2015 12:33 PM, Pavel Machek wrote:
>>>> Pavel,
>>>>
>>>> can you look into the omap4 thermal driver to see if it can be used ?
>>>
>>> After some fixes... yes, it seems to be same hardware.
>>>
>> So this should be the way to go, but then we have others claim that
>> it should not be done because the OMAP3 sensors are too unreliable
>> to use for thermal decisions. Not really sure where that leaves us.
>> I am kind of opposed to have similar drivers for similar chips
>> in two different subsystems.
>>
>> Is it possible to add the patch below to the omap thermal driver
>> and not use it for thermal decisions ?
>
> Well... noone forces you to enable the driver, and I don't think it
> will do any thermal decisions on N900 as it is ... so we should be ok.
>
> Plus, it seems to work reasonably well (say +- 5 C), so situation does
> not seem to be as bad as TI claims.
>
> Nokia was actually using it in production.
>
Ok, I'll assume that omap3 support will be added to the omap thermal driver.
Thanks,
Guenter
next prev parent reply other threads:[~2015-01-18 22:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 10:29 [PATCH] add omap34xx temperature monitoring support Pavel Machek
2014-12-26 12:34 ` [PATCH 0/3] OMAP3 temperature sensor Sebastian Reichel
2014-12-26 12:34 ` [PATCH 1/3] DT Binding for omap3 " Sebastian Reichel
2014-12-26 17:19 ` Pavel Machek
2014-12-26 23:50 ` Sebastian Reichel
2014-12-27 19:09 ` Pavel Machek
2014-12-26 12:34 ` [PATCH 2/3] hwmon: Driver for OMAP3 " Sebastian Reichel
2014-12-26 17:26 ` Pavel Machek
2014-12-27 19:24 ` Pavel Machek
2014-12-27 19:40 ` Pavel Machek
2014-12-27 19:48 ` Pavel Machek
2014-12-27 19:58 ` Pavel Machek
2014-12-27 22:35 ` Pavel Machek
2014-12-28 8:24 ` Guenter Roeck
2014-12-28 10:07 ` Sebastian Reichel
2014-12-27 23:26 ` Pavel Machek
2014-12-29 17:52 ` Grazvydas Ignotas
2014-12-29 18:01 ` Nishanth Menon
2014-12-29 18:15 ` Pavel Machek
2014-12-29 19:04 ` Guenter Roeck
2014-12-30 22:46 ` Pavel Machek
2015-01-01 9:11 ` Pavel Machek
2015-01-03 9:18 ` Pavel Machek
2015-01-07 16:19 ` Guenter Roeck
2015-01-18 20:33 ` Pavel Machek
2015-01-18 22:18 ` Guenter Roeck [this message]
2014-12-29 20:35 ` Nishanth Menon
2014-12-30 18:00 ` Pavel Machek
2014-12-26 12:34 ` [PATCH 3/3] ARM: dts: OMAP34xx/36xx: Add " Sebastian Reichel
2014-12-27 19:09 ` Pavel Machek
2014-12-26 15:54 ` [PATCH] add omap34xx temperature monitoring support Tony Lindgren
2014-12-26 16:17 ` Tony Lindgren
2014-12-26 16:26 ` Pali Rohár
2014-12-26 16:31 ` Tony Lindgren
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=54BC3130.4010401@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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