All of lore.kernel.org
 help / color / mirror / Atom feed
From: H. Nikolaus Schaller <hns@goldelico.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org, adam.ford@logicpd.com, nm@ti.com,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 2/2] ARM: omap3: Consolidate thermal references to common omap3
Date: Sat, 14 Sep 2019 11:25:35 +0200	[thread overview]
Message-ID: <40FEEAC9-8F19-466F-83C3-C8F0142D44B7@goldelico.com> (raw)
In-Reply-To: <20190913153714.30980-2-aford173@gmail.com>


> Am 13.09.2019 um 17:37 schrieb Adam Ford <aford173@gmail.com>:
> 
> Because the omap34xx, omap36xx and am3517 SoC's have the same
> thermal junction limits, there is no need to duplicate the entry
> multiple times.
> 
> This patch removes the thermal references from omap36xx and
> omap34xx and pushes it into the common omap3.dtsi file with
> the added benefit of enabling the thermal info on the AM3517.
> 
> Signed-off-by: Adam Ford <aford173@gmail.com>
> ---
> V2:	Add node name for cpu and add cooling-cells entry
> 
> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
> index 4043ecb38016..84704eb3b604 100644
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -32,7 +32,7 @@
> 		#address-cells = <1>;
> 		#size-cells = <0>;
> 
> -		cpu@0 {
> +		cpu: cpu@0 {
> 			compatible = "arm,cortex-a8";
> 			device_type = "cpu";
> 			reg = <0x0>;
> @@ -41,9 +41,14 @@
> 			clock-names = "cpu";
> 
> 			clock-latency = <300000>; /* From omap-cpufreq driver */
> +			#cooling-cells = <2>;
> 		};
> 	};

Looks ok.

> 
> +	thermal_zones: thermal-zones {
> +		#include "omap3-cpu-thermal.dtsi"
> +	};
> +

I have observed one compile issue: we also include this indirectly by am3517.dtsi
and the included code refers to <&bandgap 0> but there is no bandgap definition in am3517.dtsi

Therefore I studied the am35x TRM (SPRUGR0C) and compared to the am/dm37x TRM (SPRUGN4M).

But I can't find a bandgap temperature sensor with ADC like it is described in
"13.4.6 Band Gap Voltage and Temperature Sensor" for the am/dm37x. Only
"BANDGAP Logic" exists in both and both have the CM_FCLKEN3_CORE but with
different meaning of bit 0.

There is also no description of an CONTROL_TEMP_SENSOR (0x48002524) register for am35x.
(note: the register is also documented for omap3530).

So this might mean that the am35x does not have this feature unless TI simply
did not document it because the chip is specified for a single OPP only where it
make no sense to monitor the temperature.

We can find out only by looking at 0x48002524 if there is an undocumented
bandgap converter.

Which means we probably can't make thermal throttling work for it. And even
if the bandgap sensor exists we are lacking an value -> celsius table.


> 	pmu@54000000 {
> 		compatible = "arm,cortex-a8-pmu";
> 		reg = <0x54000000 0x800000>;
> diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi
> index f572a477f74c..b80378d6e5c1 100644
> --- a/arch/arm/boot/dts/omap34xx.dtsi
> +++ b/arch/arm/boot/dts/omap34xx.dtsi
> @@ -101,10 +101,6 @@
> 			};
> 		};
> 	};
> -
> -	thermal_zones: thermal-zones {
> -		#include "omap3-cpu-thermal.dtsi"
> -	};
> };
> 
> &ssi {
> diff --git a/arch/arm/boot/dts/omap36xx.dtsi b/arch/arm/boot/dts/omap36xx.dtsi
> index 6fb23ada1f64..ff2dca63a04e 100644
> --- a/arch/arm/boot/dts/omap36xx.dtsi
> +++ b/arch/arm/boot/dts/omap36xx.dtsi
> @@ -140,10 +140,6 @@
> 			};
> 		};
> 	};
> -
> -	thermal_zones: thermal-zones {
> -		#include "omap3-cpu-thermal.dtsi"
> -	};
> };

So if we have to exclude the am3517 we can not apply the rearrangement part
of this patch.

I'd suggest to move the cpu: cpu@0 and #cooling-cells into 1/2 (also to make it
compile stand-alone). And have the consolidation separately - if we can fix the
am3517 bandgap sensor issue.

> 
> /* OMAP3630 needs dss_96m_fck for VENC */
> -- 
> 2.17.1
> 

Tested-by: H. Nikolaus Schaller <hns@goldelico.com> # on GTA04A5 with dm3730cbp100

  reply	other threads:[~2019-09-14  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 15:37 [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family Adam Ford
2019-09-13 15:37 ` [RFC v2 2/2] ARM: omap3: Consolidate thermal references to common omap3 Adam Ford
2019-09-14  9:25   ` H. Nikolaus Schaller [this message]
2019-09-14 13:47     ` Adam Ford
2019-09-14  9:20 ` [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family H. Nikolaus Schaller
2019-09-14 13:42   ` Adam Ford
2019-09-14 14:38     ` H. Nikolaus Schaller
2019-09-14 16:12       ` Adam Ford
2019-10-07 15:11         ` Adam Ford
2019-10-07 15:44           ` H. Nikolaus Schaller
2019-10-07 17:25             ` Adam Ford
2019-10-30  8:39               ` H. Nikolaus Schaller
2019-10-30 12:00                 ` Adam Ford

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=40FEEAC9-8F19-466F-83C3-C8F0142D44B7@goldelico.com \
    --to=hns@goldelico.com \
    --cc=adam.ford@logicpd.com \
    --cc=aford173@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.