linux-kernel - Re: [PATCH v3 0/7] Switch MAIN R5F clusters to Split-mode for TI K3 Platforms

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: <172487055957.3438526.15757529252683657587.b4-ty@ti.com>
Date: Wed, 28 Aug 2024 13:43:24 -0500
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        Beleswar Padhi <b-padhi@...com>
CC: Nishanth Menon <nm@...com>, <u-kumar1@...com>, <s-anna@...com>,
        <hnagalla@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/7] Switch MAIN R5F clusters to Split-mode for TI K3 Platforms

Hi Beleswar Padhi,

On Mon, 26 Aug 2024 15:00:17 +0530, Beleswar Padhi wrote:
> TI's K3 Platforms (J7200-EVM, J721E-EVM, J721E-SK, J721S2-EVM, AM68-SK,
> J784S4-EVM, AM69-SK) have multiple R5F clusters in the MAIN domain. All
> of these clusters are configured for LockStep mode at the moment. Switch
> all of these R5F clusters to Split mode by default to maximize the
> number of R5F cores.
> 
> v3: Changelog:
> * Nishanth
> 1) Refactored changes to board level DTS files instead of SoC level dtsi files.
> 
> [...]

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

[1/7] arm64: dts: ti: k3-j7200-som-p0: Switch MAIN R5F cluster to Split-mode
      commit: 936fa8b91abac356b8c8afd70959dba8420ddc18
[2/7] arm64: dts: ti: k3-j721e-som-p0: Switch MAIN R5F clusters to Split-mode
      commit: 956d1f88a7df31cd7264b07d9ff7fe886aa96ae5
[3/7] arm64: dts: ti: k3-j721e-sk: Switch MAIN R5F clusters to Split-mode
      commit: 17613194f8f765c5559c2a1aab56b76ffbc4a2ee
[4/7] arm64: dts: ti: k3-j721s2-som-p0: Switch MAIN R5F clusters to Split-mode
      commit: ab630a7f429195a02185faec448603d2ae4b12d5
[5/7] arm64: dts: ti: k3-am68-sk-som: Switch MAIN R5F clusters to Split-mode
      commit: e1f2bf759c533fb86380ded089a16fba24222832
[6/7] arm64: dts: ti: k3-j784s4-evm: Switch MAIN R5F clusters to Split-mode
      commit: 10ef034f94ef7916c89f40e3b3844bcd066a7a58
[7/7] arm64: dts: ti: k3-am69-sk: Switch MAIN R5F clusters to Split-mode
      commit: 34d0e51ad34b0b1f8d6020020bf7e4e8e4f5cbe1

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D