linux-kernel - Re: [PATCH v2 0/4] Switch MAIN R5F clusters to Split-mode for TI SoCs

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: <20240824180744.qd7axughywodxhfg@underage>
Date: Sat, 24 Aug 2024 13:07:44 -0500
From: Nishanth Menon <nm@...com>
To: Beleswar Padhi <b-padhi@...com>
CC: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>, <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 v2 0/4] Switch MAIN R5F clusters to Split-mode for TI SoCs

On 15:21-20240821, Beleswar Padhi wrote:
> TI SoCs (J7200, J721E, J721S2 & J784S4) 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.
> 
> v2: Changelog:
> 1) Update commit messages to drop "Lockstep-mode" as default mode for early booted remoteprocs.
> 
> Link to v1:
> https://lore.kernel.org/all/20240503062414.804209-1-b-padhi@ti.com/
> 
> Apurva Nandan (1):
>   arm64: dts: ti: k3-j784s4-main: Switch MAIN R5F clusters to Split-mode
> 
> Beleswar Padhi (1):
>   arm64: dts: ti: k3-j721s2-main: Switch MAIN R5F clusters to Split-mode
> 
> Suman Anna (2):
>   arm64: dts: ti: k3-j7200-main: Switch MAIN R5F cluster to Split-mode
>   arm64: dts: ti: k3-j721e-main: Switch MAIN R5F clusters to Split-mode

Why are you doing this for all boards? if it is a specific firmware
behavior, handle that in the board dts? leave the defaults alone. don't
create surprises for downstream users.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D