From: Heiko Stuebner <heiko@sntech.de>
To: "rocky.hao" <rocky.hao@rock-chips.com>
Cc: Caesar Wang <wxt@rock-chips.com>,
rui.zhang@intel.com, edubezval@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, catalin.marinas@arm.com,
will.deacon@arm.com, huangtao@rock-chips.com,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
shawn.lin@rock-chips.com, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, cl@rock-chips.com,
william.wu@rock-chips.com, jay.xu@rock-chips.com,
xxx@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/5] arm64: dts: rockchip: add tsadc node for rk3328 SoC
Date: Fri, 11 Aug 2017 11:47:24 +0200 [thread overview]
Message-ID: <9393194.mCcQ07NuDA@phil> (raw)
In-Reply-To: <903bc8ea-a597-80b9-a2bf-551c1b6288fb@rock-chips.com>
Am Freitag, 11. August 2017, 17:45:00 CEST schrieb rocky.hao:
>
> 在 2017/8/11 14:38, Caesar Wang 写道:
> > 在 2017年08月04日 16:06, Rocky Hao 写道:
> >> add tsadc needed main information for rk3328 SoC.
> >> 50000Hz is the max clock rate supported by tsadc module.
> >>
> >> Signed-off-by: Rocky Hao <rocky.hao@rock-chips.com>
> >> ---
> >> Change in v2:
> >> - remove gerrit Change-Id
> >>
> >> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 20 ++++++++++++++++++++
> >> 1 file changed, 20 insertions(+)
> >>
> >> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> >> b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> >> index db4b2708084d..186fb93fdffd 100644
> >> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> >> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> >> @@ -308,6 +308,26 @@
> >> interrupts = <GIC_SPI 40 IRQ_TYPE_LEVEL_HIGH>;
> >> };
> >> + tsadc: tsadc@ff250000 {
> >> + compatible = "rockchip,rk3328-tsadc";
> >> + reg = <0x0 0xff250000 0x0 0x100>;
> >> + interrupts = <GIC_SPI 58 IRQ_TYPE_LEVEL_HIGH 0>;
> >> + rockchip,grf = <&grf>;
> >> + clocks = <&cru SCLK_TSADC>, <&cru PCLK_TSADC>;
> >> + clock-names = "tsadc", "apb_pclk";
> >> + assigned-clocks = <&cru SCLK_TSADC>;
> >> + assigned-clock-rates = <50000>;
> >> + resets = <&cru SRST_TSADC>;
> >> + reset-names = "tsadc-apb";
> >> + pinctrl-names = "init", "default", "sleep";
> >> + pinctrl-0 = <&otp_gpio>;
> >> + pinctrl-1 = <&otp_out>;
> >> + pinctrl-2 = <&otp_gpio>;
> >> + #thermal-sensor-cells = <1>;
> >
> > Only one sensor, so maybe the value should be 0.
> Caesar, #thermal-sensor-cells means parameter counts used to match the
> proper sensor registered. Both 0 and 1 work well.
>
> Case 0, i.e. #thermal-sensor-cells = <0>, it uses the default channel
> number 0 to match tsadc channal.
> Case 1, i.e. #thermal-sensor-cells = <1>, it uses the setting
> "thermal-sensors = <&tsadc 0>;" to match tsadc channal.
>
> Case 1 provides more readable info than case 0. By my understanding,
> using the default value such as case 0, is not a good coding style.
Also, the binding for the tsadc controller specifies
#thermal-sensor-cells: 1
And the IP block in general can of course handle multiple channels,
so it should also stay that way in the dts.
Heiko
> >
> >> + rockchip,hw-tshut-temp = <100000>;
> >> + status = "disabled";
> >> + };
> >> +
> >> saradc: adc@ff280000 {
> >> compatible = "rockchip,rk3328-saradc",
> >> "rockchip,rk3399-saradc";
> >> reg = <0x0 0xff280000 0x0 0x100>;
> >
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2017-08-11 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 8:06 [PATCH v2 0/5] thermal: rockchip: add tsadc support in thermal driver and IPA thermal control for rk3328 in dts Rocky Hao
2017-08-04 8:06 ` [PATCH v2 1/5] dt-bindings: rockchip-thermal: Support the RK3328 SoC compatible Rocky Hao
2017-08-10 17:49 ` Rob Herring
2017-08-11 1:08 ` rocky.hao
2017-08-04 8:06 ` [PATCH v2 2/5] thermal: rockchip: Support the RK3328 SOC in thermal driver Rocky Hao
2017-08-11 6:32 ` Caesar Wang
2017-08-04 8:06 ` [PATCH v2 4/5] arm64: dts: rockchip: add thermal nodes for rk3328 SoC Rocky Hao
2017-08-11 6:44 ` Caesar Wang
2017-08-11 9:46 ` rocky.hao
[not found] ` <f0c7ab33-1b7b-8b9d-fd20-aa84001014cc-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-11 9:48 ` Heiko Stuebner
[not found] ` <1501833976-1100-5-git-send-email-rocky.hao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-11 15:19 ` Heiko Stuebner
[not found] ` <1501833976-1100-1-git-send-email-rocky.hao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-04 8:06 ` [PATCH v2 3/5] arm64: dts: rockchip: add tsadc node " Rocky Hao
2017-08-11 6:38 ` Caesar Wang
2017-08-11 9:45 ` rocky.hao
2017-08-11 9:47 ` Heiko Stuebner [this message]
2017-08-11 15:18 ` Heiko Stuebner
2017-08-04 8:09 ` [PATCH v2 5/5] arm64: dts: rockchip: Enable tsadc module on RK3328 eavluation board Rocky Hao
2017-08-11 15:19 ` Heiko Stuebner
2017-08-11 4:51 ` [PATCH v2 0/5] thermal: rockchip: add tsadc support in thermal driver and IPA thermal control for rk3328 in dts Zhang Rui
2017-08-11 6:22 ` rocky.hao
2017-08-11 6:27 ` Heiko Stuebner
2017-08-11 8:01 ` Zhang Rui
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=9393194.mCcQ07NuDA@phil \
--to=heiko@sntech.de \
--cc=catalin.marinas@arm.com \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rocky.hao@rock-chips.com \
--cc=rui.zhang@intel.com \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=william.wu@rock-chips.com \
--cc=wxt@rock-chips.com \
--cc=xxx@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).