From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.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
Subject: Re: [PATCH] arm64: dts: qcom: purwa: deduplicate thermal sensors with Hamoa
Date: Tue, 24 Mar 2026 10:25:30 +0100 [thread overview]
Message-ID: <7d13d449-17e5-4838-b4bf-f9ce14e1142e@oss.qualcomm.com> (raw)
In-Reply-To: <xy2jzlamtkpqfpcpegoysyh6u2cnfubkz5233yvuuzfutzpxkf@w3inytibm3sq>
On 3/23/26 5:49 PM, Dmitry Baryshkov wrote:
> On Mon, Mar 23, 2026 at 04:21:00PM +0100, Konrad Dybcio wrote:
>> On 3/20/26 3:33 AM, Dmitry Baryshkov wrote:
>>> Hamoa and Purwa have pretty close thermal zones definitions. The major
>>> difference is that several zones are absent (because of the lack of the
>>> CPU cluster) and several zones use tsens2 instead of tsens3.
>>>
>>> Instead of completely duplicating thermal zones for Purwa, reuse themal
>>> zones from Hamoa, patching them where required.
>>>
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>>> ---
>>
>> Slightly reluctantly:
>
> Why? I'd really interested here.
I suppose my reluctance comes from the decreased readability, but then
I suppose the silicon is not going to change if we get it right once, so
it's not a real concern..
Konrad
next prev parent reply other threads:[~2026-03-24 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 2:33 Dmitry Baryshkov
2026-03-21 9:40 ` Abel Vesa
2026-03-23 15:21 ` Konrad Dybcio
2026-03-23 16:49 ` Dmitry Baryshkov
2026-03-24 9:25 ` Konrad Dybcio [this message]
2026-03-24 23:13 ` Dmitry Baryshkov
2026-03-26 2:44 ` Bjorn Andersson
2026-03-26 3:19 ` Bjorn Andersson
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=7d13d449-17e5-4838-b4bf-f9ce14e1142e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®