[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 09 Sep 2014 13:37:31 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Caesar Wang <caesar.wang@...k-chips.com>
Cc: rui.zhang@...el.com, edubezval@...il.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, huangtao@...k-chips.com,
cf@...k-chips.com, dianders@...omium.org, dtor@...omium.org,
zyw@...k-chips.com, addy.ke@...k-chips.com,
dmitry.torokhov@...il.com
Subject: Re: [PATCH v4 3/4] ARM: dts: add main Thermal info to rk3288
Am Mittwoch, 3. September 2014, 10:10:38 schrieb Caesar Wang:
> Signed-off-by: Caesar Wang <caesar.wang@...k-chips.com>
> ---
> arch/arm/boot/dts/rk3288.dtsi | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
> index 36be7bb..3d672e3 100644
> --- a/arch/arm/boot/dts/rk3288.dtsi
> +++ b/arch/arm/boot/dts/rk3288.dtsi
> @@ -224,6 +224,17 @@
> status = "disabled";
> };
>
> + tsadc: tsadc@...80000 {
please keep the list of nodes sorted by register address. So when looking at
my v3.18-next/dts branch, it should be after uart4: serial@...c0000 and before
usb_host0_ehci: usb@...00000 .
> + 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-1 = <&tsadc_int>;
> + status = "disabled";
> + };
> +
> /* NOTE: ohci@...20000 doesn't actually work on hardware */
>
> usb_hsic: usb@...c0000 {
> @@ -611,5 +622,12 @@
> rockchip,pins = <5 15 3 &pcfg_pull_none>;
> };
> };
> +
> + tsadc {
> + tsadc_int: tsadc-int {
> + rockchip,pins = <0 10 RK_FUNC_1 &pcfg_pull_up>;
> + };
> + };
After looking this up in the schematics I see that this is the
overtemperature-protection output pin ... labeled OTP_OUT.
So I'd think the pinconfig should reflect this pin-name, especially as tsadc-int
suggests, that this would be an interrupt leading into the tsadc, while in
fact it is an output to a separate circuit.
Heiko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists