From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] thermal: rockchip: add driver for thermal
Date: Thu, 28 Aug 2014 10:37:35 -0400 [thread overview]
Message-ID: <20140828143733.GA18084@developer> (raw)
In-Reply-To: <2852853.mfRZfFVSev@wuerfel>
Ceasar and Arnd,
On Thu, Aug 28, 2014 at 10:48:23AM +0200, Arnd Bergmann wrote:
> On Thursday 28 August 2014 08:59:19 Caesar Wang wrote:
> > Thermal is TS-ADC Controller module supports user-defined mode and automatic mode.
> >
> > User-defined mode refers,TSADC all the control signals entirely by software
> > writing to register for direct control.
> >
> > Automaic mode refers to the module automatically poll TSADC output,and the results
> > Were checked.
> >
> > If you find that the temperature High in a period of time, an interrupt is generated
> > to the processor down-measures taken;if the temperature over a period of time High,
> > the resulting TSHUT gave CRU module,let it reset the entire chip, or via GPIO give PMIC.
> >
> > Signed-off-by: zhaoyifeng <zyf@rock-chips.com>
> > Signed-off-by: Caesar Wang <caesar.wang@rock-chips.com>
>
> Hi Caesar,
>
> After looking at the driver (last time I only received the patch for
> the binding), I have a more general comment:
>
> This looks like a general-purpose ADC device, not an IP block that is
> specific to thermal management. The binding looks ok for that purpose
> but should probably be moved into Documentation/devicetree/bindings/iio/adc/
> as a minor change.
>
I agree with Arnd's point here. It makes sense to me to have this driver
under the IIO umbrella.
> On the driver side, I believe the correct way to deal with this setup
> is to split your driver into a generic drivers/iio/adc/rockchips-tsadc.c
> file, and a smaller thermal driver that uses the iio in-kernel interfaces,
> ideally one that is independent of the underlying hardware and can
> work on any ADC implementation.
>
Agreed. If you can write such interface and make your driver to work in
such way, that would be great.
> I've put the IIO maintainer on Cc in this mail, maybe Jonathan or someone
> else on the linux-iio mailing list has some extra insight.
>
> Arnd
Cheers,
Eduardo
next prev parent reply other threads:[~2014-08-28 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 0:59 [PATCH v3 0/4] Rockchip soc theamal driver Caesar Wang
2014-08-28 0:59 ` [PATCH v3 1/4] thermal: rockchip: add driver for thermal Caesar Wang
2014-08-28 8:48 ` Arnd Bergmann
2014-08-28 14:37 ` Eduardo Valentin [this message]
2014-08-28 16:11 ` Heiko Stübner
2014-08-28 16:16 ` Arnd Bergmann
2014-08-28 19:36 ` Caesar Wang
2014-08-28 23:01 ` Heiko Stübner
[not found] ` <2014082909531345696848@rock-chips.com>
2014-08-29 11:39 ` edubezval at gmail.com
2014-08-29 12:08 ` Huang Tao
2014-08-30 9:30 ` Jonathan Cameron
2014-08-28 0:59 ` [PATCH v3 2/4] dt-bindings: document Rockchip thermal Caesar Wang
2014-08-28 0:59 ` [PATCH v3 3/4] ARM: dts: add main Thermal info to rk3288 Caesar Wang
2014-08-28 0:59 ` [PATCH v4 4/4] ARM: dts: enable Thermal on rk3288-evb board Caesar Wang
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=20140828143733.GA18084@developer \
--to=edubezval@gmail.com \
--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).