public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Caesar Wang <caesar.wang@rock-chips.com>
To: "Arnd Bergmann" <arnd@arndb.de>, "Heiko Stübner" <heiko@sntech.de>
Cc: Eduardo Valentin <edubezval@gmail.com>,
	rui.zhang@intel.com, grant.likely@linaro.org, robh+dt@kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, huangtao@rock-chips.com,
	cf@rock-chips.com, dianders@chromium.org, dtor@chromium.org,
	zyw@rock-chips.com, addy.ke@rock-chips.com,
	dmitry.torokhov@gmail.com, zhaoyifeng <zyf@rock-chips.com>,
	linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v3 1/4] thermal: rockchip: add driver for thermal
Date: Fri, 29 Aug 2014 03:36:36 +0800	[thread overview]
Message-ID: <53FF84C4.9080902@rock-chips.com> (raw)
In-Reply-To: <4488604.oBeB6it8Vr@wuerfel>

Arnd & Heiko & Eduardo,

OK. Maybe you are right.

This driver should be put into drivers/iio/adc/* ,
Anyway,I will re-edit it ASAP.


在 2014/8/29 0:16, Arnd Bergmann 写道:
> On Thursday 28 August 2014 18:11:43 Heiko Stübner wrote:
>> Am Donnerstag, 28. August 2014, 10:37:35 schrieb Eduardo Valentin:
>>>> 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.
>> But I currently don't see how you would model the temperature handling parts
>> from a generic thermal driver to a generic adc driver for the rk3288-tsadc.
>>
>> I guess the general temperature irq handling would use iio-triggers? But how
>> does the target temperature get into the TSADC_COMP1_INT register.
>>
>> Also when getting the temperature, Caesar's driver compares it to its trip
>> points and sets the next trip point depending on the current temperature
>> (passive <-> critical) in rockchip_get_temp.
>>
>> Maybe there is some completely easy way for this, but currently I don't see
>> it.
> Eduardo earlier today replied to an email about a generic driver for
> thermal, which was posted in February but hasn't been merged.
> See https://lkml.org/lkml/2014/2/5/810
>
> There may be a newer version of this patch, which I haven't found.
>
> 	Arnd
>
>
>

-- 
Best regards,
Caesar



  reply	other threads:[~2014-08-28 19:36 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
2014-08-28 16:11       ` Heiko Stübner
2014-08-28 16:16         ` Arnd Bergmann
2014-08-28 19:36           ` Caesar Wang [this message]
2014-08-28 23:01             ` Heiko Stübner
     [not found]         ` <2014082909531345696848@rock-chips.com>
2014-08-29 11:39           ` edubezval
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=53FF84C4.9080902@rock-chips.com \
    --to=caesar.wang@rock-chips.com \
    --cc=addy.ke@rock-chips.com \
    --cc=arnd@arndb.de \
    --cc=cf@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor@chromium.org \
    --cc=edubezval@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=zyf@rock-chips.com \
    --cc=zyw@rock-chips.com \
    /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