From: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@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>,
Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490-rb3gen2: Adjust tsens thermal zone configuration
Date: Tue, 16 Dec 2025 13:01:01 +0530 [thread overview]
Message-ID: <46cc0587-8eb6-4638-ad04-c05dcd56718c@oss.qualcomm.com> (raw)
In-Reply-To: <zf5ztvnzaf6tplpjpytwbhktrebdnst2doybuubp6rjfj2fjs7@t2ma4ylx67gx>
Hi Dmitry,
On 12/16/2025 1:21 AM, Dmitry Baryshkov wrote:
> On Mon, Dec 15, 2025 at 04:29:34PM +0530, Manaf Meethalavalappu Pallikunhi wrote:
>> The QCS6490 rb3gen2 board uses the same Qualcomm QCM6490 platform
> Is there a difference between QCS6490 and QCM6490 or between QC[SM]6490
> and SC7280?
Difference is only for qcs6490-rb3gen2 (IOT ).
>
>> but has a different thermal junction temperature specification
>> due to package-level differences.
>>
>> Update passive/hot trip thresholds to 105°C and critical trip
>> thresholds to 115°C for various subsystem TSENS sensors.
>>
>> Disable CPU cooling maps for CPU TSENS since CPU thermal mitigation
>> is handled automatically in hardware on this board.
> Is it a peculiarity of the RB3 Gen2 or is it that Chrome devices didn't
> do it? What about QCM6490 IDP or FairPhone FP5?
Chrome devices do not perform automatic thermal mitigation, whereas all
other boards handle it automatically. I will push another patch to
disable cpu mitigation for all other boards other than chrome.
Thanks,
Manaf
>
>> Signed-off-by: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 334 +++++++++++++++++++
>> 1 file changed, 334 insertions(+)
>>
next prev parent reply other threads:[~2025-12-16 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 10:59 Manaf Meethalavalappu Pallikunhi
2025-12-15 19:51 ` Dmitry Baryshkov
2025-12-16 7:31 ` Manaf Meethalavalappu Pallikunhi [this message]
2025-12-17 11:16 ` Konrad Dybcio
2026-01-03 18:05 ` Bjorn Andersson
2026-02-17 13:38 ` Konrad Dybcio
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=46cc0587-8eb6-4638-ad04-c05dcd56718c@oss.qualcomm.com \
--to=manaf.pallikunhi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gaurav.kohli@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®