Re: [PATCH v11 4/5] ARM: dts: add main Thermal info to rk3288

From: Dmitry Torokhov
Date: Thu Oct 16 2014 - 17:53:27 EST


Hi Caesar,

On Thu, Oct 16, 2014 at 09:31:40PM +0800, Caesar Wang wrote:
> This patch is depend on rk3288-thermal.dtsi,or
> it will compile error.
>
> If the temperature over a period of time High,over 120C
> the resulting TSHUT gave CRU module,let it reset
> the entire chip,or via GPIO give PMIC.
>
> Signed-off-by: Caesar Wang <caesar.wang@xxxxxxxxxxxxxx>
> ---
> arch/arm/boot/dts/rk3288.dtsi | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
> index cb18bb4..bf34111 100644
> --- a/arch/arm/boot/dts/rk3288.dtsi
> +++ b/arch/arm/boot/dts/rk3288.dtsi
> @@ -15,6 +15,7 @@
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> #include <dt-bindings/pinctrl/rockchip.h>
> #include <dt-bindings/clock/rk3288-cru.h>
> +#include <dt-bindings/thermal/thermal.h>
> #include "skeleton.dtsi"
>
> / {
> @@ -346,6 +347,19 @@
> status = "disabled";
> };
>
> + 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";
> + pinctrl-names = "default";
> + pinctrl-0 = <&otp_out>;
> + #thermal-sensor-cells = <1>;
> + hw-shut-temp = <120000>;
> + status = "disabled"

It looks like you are missing semicolon here.

> + };
> +
> usb_host0_ehci: usb@ff500000 {
> compatible = "generic-ehci";
> reg = <0xff500000 0x100>;
> @@ -965,6 +979,12 @@
> };
> };
>
> + tsadc {
> + otp_out: otp-out {
> + rockchip,pins = <0 10 RK_FUNC_1 &pcfg_pull_none>;
> + };
> + };
> +
> pwm0 {
> pwm0_pin: pwm0-pin {
> rockchip,pins = <7 0 RK_FUNC_1 &pcfg_pull_none>;
> --
> 1.9.1
>
>

--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/