[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZnFySuwi-Hz6DNDM@hovoldconsulting.com>
Date: Tue, 18 Jun 2024 13:40:58 +0200
From: Johan Hovold <johan@...nel.org>
To: Abel Vesa <abel.vesa@...aro.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Rajendra Nayak <quic_rjendra@...cinc.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: x1e80100: Enable tsens and thermal
zone nodes
On Tue, Jun 18, 2024 at 01:00:06PM +0300, Abel Vesa wrote:
> On 24-06-17 11:24:22, Johan Hovold wrote:
> > The CPU bottom thermal zones fail to register with v2:
> >
> > [ 0.146219] thermal_sys: Thermal zone name (cpu0-0-bottom-thermal) too long, should be under 20 chars
>
> Urgh, did not test after renaming the zones.
>
> Talking to Daniel Lezcano, he seems to suggest that the size can become
> dynamic at some point. For now will switch back to
> cpu0-0-0-bottom-thermal and cpuss0-0-thermal. So that's O for top and 1
> for bottom.
Did you mean to say 'cpu0-0-0-thermal' and 'cpu0-0-1-thermal'?
Abbreviating 'bottom' (e.g. as 'btm') also works and may be preferred as
it's not very obvious what any of the zeroes in 'cpu0-0-0-thermal' stand
for.
Johan
Powered by blists - more mailing lists