From: Tomeu Vizoso <tomeu@tomeuvizoso.net>
To: Caesar Wang <caesar.wang@rock-chips.com>
Cc: heiko@sntech.de, rui.zhang@intel.com, edubezval@gmail.com,
Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-doc@vger.kernel.org, huangtao@rock-chips.com,
cf@rock-chips.com, dianders@chromium.org, dtor@chromium.org,
dmitry.torokhov@gmail.com, addy.ke@rock-chips.com,
zyf@rock-chips.com, cjf@rock-chips.com
Subject: Re: [PATCH v5 2/4] dt-bindings: document Rockchip thermal
Date: Thu, 18 Sep 2014 11:27:45 +0200 [thread overview]
Message-ID: <CAAObsKA61Ano85P6PehOY7WqR0FgTz_Rfur8UAt56ZXoNyoyqQ@mail.gmail.com> (raw)
In-Reply-To: <1410926353-15674-3-git-send-email-caesar.wang@rock-chips.com>
On 17 September 2014 05:59, Caesar Wang <caesar.wang@rock-chips.com> wrote:
> This add the necessary binding documentation for the thermal
> found on Rockchip SoCs
Hi Caesar,
is there any reason to not use the existing thermal bindings? You can
find a description in
Documentation/devicetree/bindings/thermal/thermal.txt and example code
in omap, or in the patches for Tegra recently posted by Mikko
Perttunen.
Regards,
Tomeu
> Signed-off-by: zhaoyifeng <zyf@rock-chips.com>
> Signed-off-by: Caesar Wang <caesar.wang@rock-chips.com>
> ---
> .../bindings/thermal/rockchip-thermal.txt | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/rockchip-thermal.txt
>
> diff --git a/Documentation/devicetree/bindings/thermal/rockchip-thermal.txt b/Documentation/devicetree/bindings/thermal/rockchip-thermal.txt
> new file mode 100644
> index 0000000..6fc8bc3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/rockchip-thermal.txt
> @@ -0,0 +1,41 @@
> +* Temperature Sensor ADC (TSADC) on rockchip SoCs
> +
> +Required properties:
> +- compatible: "rockchip,rk3288-tsadc"
> +- reg: physical base address of the controller and length of memory mapped
> + region.
> +- interrupts: The interrupt number to the cpu. The interrupt specifier format
> + depends on the interrupt controller.
> +- clocks: Must contain an entry for each entry in clock-names.
> +- clock-names: Shall be "tsadc" for the converter-clock, and "apb_pclk" for
> + the peripheral clock.
> +- num-trips: number of total trip points, this is required, set it 0 if none,
> + if greater than 0, the following properties must be defined;
> +- tripN-temp: temperature of trip point N, should be in ascending order;
> +- tripN-type: type of trip point N, should be one of "active" "passive" "hot"
> + "critical";
> +- tripN-cdev-num: number of the cooling devices which can be bound to trip
> + point N, this is required if trip point N is defined, set it 0 if none,
> + otherwise the following cooling device names must be defined;
> +- tripN-cdev-nameM: name of the No. M cooling device of trip point N;
> +
> +Example:
> +tsadc: tsadc@ff280000 {
> + compatible = "rockchip,rk3288-tsadc";
> + reg = <0xff280000 0x100>;
> + interrupts = <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru SCLK_TSADC>, <&cru PCLK_TSADC>;
> + clock-names = "tsadc", "apb_pclk";
> +
> + num-trips = <2>;
> +
> + trip0-temp = <80>;
> + trip0-type = "passive";
> + trip0-cdev-num = <1>;
> + trip0-cdev-name0 = "thermal-cpufreq-0";
> +
> + trip1-temp = <100>;
> + trip1-type = "critical";
> + trip1-cdev-num = <1>;
> + trip1-cdev-name0 = "thermal-cpufreq-0";
> +};
> --
> 1.9.1
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-18 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 3:59 [PATCH v5 0/4] Rockchip soc thermal driver Caesar Wang
[not found] ` <1410926353-15674-1-git-send-email-caesar.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-17 3:59 ` [PATCH v5 1/4] thermal: rockchip: add driver for Thermal Caesar Wang
2014-09-17 17:02 ` Dmitry Torokhov
2014-09-18 8:31 ` Caesar Wang
2014-09-18 17:02 ` Dmitry Torokhov
2014-09-17 3:59 ` [PATCH v5 2/4] dt-bindings: document Rockchip thermal Caesar Wang
[not found] ` <1410926353-15674-3-git-send-email-caesar.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-17 19:48 ` Doug Anderson
2014-09-17 20:13 ` Dmitry Torokhov
2014-09-18 2:33 ` Caesar Wang
2014-09-18 9:27 ` Tomeu Vizoso [this message]
2014-09-18 13:25 ` Caesar Wang
2014-09-18 14:19 ` Tomeu Vizoso
2014-09-18 17:18 ` Dmitry Torokhov
2014-09-17 3:59 ` [PATCH v5 3/4] ARM: dts: add main Thermal info to rk3288 Caesar Wang
2014-09-17 3:59 ` [PATCH v5 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=CAAObsKA61Ano85P6PehOY7WqR0FgTz_Rfur8UAt56ZXoNyoyqQ@mail.gmail.com \
--to=tomeu@tomeuvizoso.net \
--cc=addy.ke@rock-chips.com \
--cc=arnd@arndb.de \
--cc=caesar.wang@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=cjf@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=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--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=rui.zhang@intel.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).