From: Caesar Wang <caesar.wang@rock-chips.com>
To: heiko@sntech.de, rui.zhang@intel.com, edubezval@gmail.com
Cc: dmitry.torokhov@gmail.com, arnd@arndb.de, zyf@rock-chips.com,
dianders@chromium.org, cjf@rock-chips.com,
zhengsq@rock-chips.com, linux-rockchip@list.infradead.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, cf@rock-chips.com,
dbasehore@chromium.org, Caesar Wang <caesar.wang@rock-chips.com>
Subject: [PATCH v6 0/3] Rockchip soc thermal driver
Date: Fri, 26 Sep 2014 22:33:09 +0800 [thread overview]
Message-ID: <1411741992-18890-1-git-send-email-caesar.wang@rock-chips.com> (raw)
Changes in v6:
* address comments from Tomeu Vizoso.
- use thermal's generic framework.
Changes in v5:
* address comments from Eduardo Valentin,rui.zhang and Heiko Stubner:
- with BIT() macro
- manage clocks in suspend/resume.
- license is fixed as GPLv2 .
- #include "thermal_core.h"->#include <linux/thermal.h>
- use the generic trip-points.the hw-shut-temp isn't generic trip-points.
- The method of binding and unbinding be fixed.
- The pin-name tsadc->otp_out
Changes in v4:
* address comments from Jonathan Cameron,huangtao and zhaoyifeng:
- this series thermal driver still be put in driver/thermal/
- modify the thermal driver description.
Changes in v3:(add dts configure)
* address comments from Dmitry Torokhov and Arnd Bergmann:
- fix clock-names in rockchip-thermal.txt
- remove rockchip_thermal_control() in rockchip_set_mode()
- fix some code style.
- add dts configure.
Changes in v2:
* address comments from Heiko Stubner:
- fix dt-bindings in rockchip-thermal.txt
- remove Author mark
- rename TSADC_XXX->TSADCV2_XXX,it eill ready to merge compatible other SoCs.
- fix a identation
- remove clk_set_rate(),it's no necessary.
- fix the SIMPLE_DEV_PM_OPS() function style.
Tested on rk3288 SDK board and pinky-v1 board.
Caesar Wang (3):
thermal: rockchip: add driver for Thermal
dt-bindings: document Rockchip thermal
ARM: dts: add main Thermal info to rk3288
.../bindings/thermal/rockchip-thermal.txt | 32 ++
arch/arm/boot/dts/rk3288.dtsi | 44 ++
drivers/thermal/Kconfig | 10 +
drivers/thermal/Makefile | 1 +
drivers/thermal/rockchip_thermal.c | 605 +++++++++++++++++++++
5 files changed, 692 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/rockchip-thermal.txt
create mode 100644 drivers/thermal/rockchip_thermal.c
--
1.9.1
next reply other threads:[~2014-09-26 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 14:33 Caesar Wang [this message]
2014-09-26 14:33 ` [PATCH v6 1/3] thermal: rockchip: add driver for Thermal Caesar Wang
2014-09-26 14:33 ` [PATCH v6 2/3] dt-bindings: document Rockchip thermal Caesar Wang
2014-09-26 14:33 ` [PATCH v6 3/3] ARM: dts: add main Thermal info to rk3288 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=1411741992-18890-1-git-send-email-caesar.wang@rock-chips.com \
--to=caesar.wang@rock-chips.com \
--cc=arnd@arndb.de \
--cc=cf@rock-chips.com \
--cc=cjf@rock-chips.com \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=edubezval@gmail.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@list.infradead.org \
--cc=rui.zhang@intel.com \
--cc=zhengsq@rock-chips.com \
--cc=zyf@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;
as well as URLs for NNTP newsgroup(s).