linux-kernel - Re: [PATCH 0/2] arm64: dts: ti: k3-am62p|j722s: Add passive trip points

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: <175205768444.924566.10610235115148189827.b4-ty@ti.com>
Date: Fri, 11 Jul 2025 10:35:41 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Joao Paulo Goncalves <jpaulo.silvagoncalves@...il.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        Joao Paulo Goncalves
	<joao.goncalves@...adex.com>
Subject: Re: [PATCH 0/2] arm64: dts: ti: k3-am62p|j722s: Add passive trip points

Hi João Paulo Gonçalves,

On Mon, 23 Jun 2025 13:12:25 -0300, João Paulo Gonçalves wrote:
> Enable CPU frequency throttling on AM62P/J722S when an alert temperature
> threshold is reached before the critical temperature for shutdown.
> 
> Adjust Verdin AM62P thermal threshold accordingly to the SoM
> thermal specification.
> 
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-am62p-j722s: Enable freq throttling on thermal alert
      commit: f02dccbe9641c4be467d22f4d5712523d902e94d
[2/2] arm64: dts: ti: k3-am62p-verdin: Adjust temperature trip points
      commit: 3b08f8a34a2061d89a2411d04a675b3860d4f9cc

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh