Dear Eduardo Bezerra Valentin:

? 2014?08?29? 19:39, edubezval at gmail.com ??:

Hello Zhao,

On Thu, Aug 28, 2014 at 9:54 PM, ??? [off-list ref] wrote:

quoted

Hi Heiko?

   The TS-ADC on RK3288 has two component, a tsadc and a tsadc controller.
The tsadc controller is similar like the thermal manager unit on other SOCs.
We followed the naming of 3066, but not named as the Thermal Manager.

   Moreover,there is only one set of apb registers to access the tsadc
controller,and the tsadc is controlled by the tsadc controller,could not
access directly. If we write a general tsadc driver by accessed tsadc
controller registers, and it hardly to write a driver for the tsadc
controller.

As suggested by Arnd, you can use the generic driver as interface
between thermal framework and IIO layer. The driver you are going to
write to your ADC is going to be in the IIO subsystem. The only
difference is that the generic driver would work for any ADC driver in
the IIO subsystem.
https://lkml.org/lkml/2014/2/5/810

In fact, there is already a generic driver. We just need to get it up
to date.  I see some testing has been already done, and results sound
promising.

This iio_thermal driver only support get temperature from the ADC IIO
channel.
It dose not support any advanced feature such as configure the
temperature when system should be reset.
So if we adapt it, we will access the register form both TSADC IIO
driver and  thermal driver.
I don't thank this is a good ideal.

In fact, we should ignore the "ADC" stuff. This sensor use ADC internal,
but it is transparent to software, especially in automatic mode.

quoted

   So, I do not agree to write a generic adc driver for the rk3288-tsadc.

________________________________
Yifeng Zhao