From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: x1e80100: Enable tsens and thermal zone nodes
Date: Tue, 18 Jun 2024 13:40:58 +0200 [thread overview]
Message-ID: <ZnFySuwi-Hz6DNDM@hovoldconsulting.com> (raw)
In-Reply-To: <ZnFapqOxQBK5YViU@linaro.org>
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
next prev parent reply other threads:[~2024-06-18 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:50 [PATCH v2] arm64: dts: qcom: x1e80100: Enable tsens and thermal zone nodes Abel Vesa
2024-06-17 9:24 ` Johan Hovold
2024-06-18 10:00 ` Abel Vesa
2024-06-18 11:40 ` Johan Hovold [this message]
2024-06-18 11:06 ` Konrad Dybcio
2024-06-20 12:52 ` Abel Vesa
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=ZnFySuwi-Hz6DNDM@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
/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