[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170904134347.9FF0.4A936039@socionext.com>
Date: Mon, 04 Sep 2017 13:43:48 +0900
From: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Masami Hiramatsu <masami.hiramatsu@...aro.org>,
Jassi Brar <jaswinder.singh@...aro.org>
Subject: Re: [PATCH v3 2/2] arm64: dts: uniphier: add nodes of thermal monitor and thermal zone for LD20
Yamada-san,
On Thu, 10 Aug 2017 19:48:22 +0900 <yamada.masahiro@...ionext.com> wrote:
> Hi Hayashi-san,
>
>
> 2017-07-05 20:53 GMT+09:00 Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>:
> > Add nodes of thermal monitor and thermal zone for UniPhier LD20 SoC.
> > The thermal monitor is included in sysctrl.
> >
> > Furthermore, since the reference board doesn't have a calibrated value of
> > thermal monitor, this patch gives the default value for LD20 reference
> > board.
> >
> > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
> > ---
> > .../arm64/boot/dts/socionext/uniphier-ld20-ref.dts | 4 +++
> > arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 40 ++++++++++++++++++++++
> > 2 files changed, 44 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts b/arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts
> > index 609162a..d7f6b39 100644
> > --- a/arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts
> > +++ b/arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts
> > @@ -86,3 +86,7 @@
> > &i2c0 {
> > status = "okay";
> > };
> > +
> > +&pvtctl {
> > + socionext,tmod-calibration = <0x0f22 0x68ee>;
> > +};
>
>
> I think this calib value is shared among all boards
> (ref and global).
>
>
> Please move it to the SoC dtsi.
I see. I'll move it.
> > + cooling-maps {
> > + map0 {
> > + trip = <&cpu_alert>;
> > + cooling-device = <&cpu0 (-1) (-1)>;
> > + };
> > + map1 {
> > + trip = <&cpu_alert>;
> > + cooling-device = <&cpu2 (-1) (-1)>;
> > + };
> > + };
> > + };
> > + };
> > +
>
> After all, I decided to use dt-bindings headers.
> Could you use THERMAL_NO_LIMIT for clarification?
Okay, I'll replace '(-1)' to THERMAL_NO_LIMIT and add the '#include' directive.
---
Best Regards,
Kunihiko Hayashi
Powered by blists - more mailing lists