[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200817215953.59607c11@aktux>
Date: Mon, 17 Aug 2020 21:59:53 +0200
From: Andreas Kemnade <andreas@...nade.info>
To: Adam Ford <aford173@...il.com>
Cc: linux-omap@...r.kernel.org, aford@...conembedded.com,
BenoƮt Cousson
<bcousson@...libre.com>, Tony Lindgren <tony@...mide.com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, hns@...delico.com
Subject: Re: [PATCH V2] ARM: dts: omap3: Add cpu trips and cooling map for
omap34/36 families
On Mon, 17 Aug 2020 08:39:31 -0500
Adam Ford <aford173@...il.com> wrote:
> The OMAP3530, OMAP3630, and DM3730 all show thresholds of 90C and 105C
> depending on commercial or industrial temperature ratings.
>
> This patch expands the thermal information to include the limits of 90
> and 105C for alert and critical. It sets the coolings-cells for the
> 34xx and 36xx CPU's which both point to omap3-cpu-thermal.dtsi.
>
> For boards who never use industrial temperatures, these can be
> changed on their respective device trees with something like:
>
> &cpu_alert0 {
> temperature = <85000>; /* millicelsius */
> };
>
> &cpu_crit {
> temperature = <90000>; /* millicelsius */
> };
>
> OMAP3_THERMAL will need to be enabled. It is off by default.
>
hmm, I think the patch for idling core when OMAP3_THERMAL is enabled
got stuck somewhere. It still seems not to work. Shouldn't that patch
be applied first?
Regards,
Andreas
Powered by blists - more mailing lists