lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <oekmcxiltaiynuwt2p4g2grae4gyud7vn5usw3v2cp4vwyfr5c@gg2x4lqvtd4n>
Date: Sat, 3 Jan 2026 12:05:03 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@....qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, 
	Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Gaurav Kohli <gaurav.kohli@....qualcomm.com>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490-rb3gen2: Adjust tsens thermal
 zone configuration

On Tue, Dec 16, 2025 at 01:01:01PM +0530, Manaf Meethalavalappu Pallikunhi wrote:
> 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.
> 

This matches what we're doing everywhere else (i.e. rely on LMh/OSM/EPSS
to do the fast throttling of cores), so I'd expect that this should
apply to all non-Chrome boards...

Instead of doing this for every board, can we push the cpu/cooling-maps
into e.g. sc7280-chrome-common.dtsi?

If I understand you correctly, we'd still have the desire to adjust the
temperature values, but that's a smaller per-board change.

Regards,
Bjorn

> Thanks,
> 
> Manaf
> 
> > 
> > > Signed-off-by: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@....qualcomm.com>
> > > ---
> > >   arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 334 +++++++++++++++++++
> > >   1 file changed, 334 insertions(+)
> > > 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ