linux-kernel - Re: [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware

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: <172487140504.3441749.10326233588807171364.b4-ty@ti.com>
Date: Wed, 28 Aug 2024 13:58:39 -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>, <tony@...mide.com>,
        <bb@...com>, <d-gole@...com>, <afd@...com>, <hnagalla@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware

Hi Beleswar Padhi,

On Mon, 26 Aug 2024 16:18:13 +0530, Beleswar Padhi wrote:
> The remoteproc firmware like of R5F and DSPs in the MAIN voltage domain
> use timers. At the same time, if Linux probes the timers, some
> instability is observed while booting remote cores. Therefore, change
> the status of the timer nodes to "reserved" to avoid any clash.
> 
> NOTE: This series has been rebased on top of a sibling series[0] as both of them
> introduce changes in the same files. Thus, please apply [0] before applying this
> series.
> 
> [...]

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

[1/7] arm64: dts: ti: k3-j7200-som-p0: Change timer nodes status to reserved
      commit: f7d6dacb233e1fe7e99e766abddd2a0247957d80
[2/7] arm64: dts: ti: k3-j721e-som-p0: Change timer nodes status to reserved
      commit: 96b2d17bfe407faae341053e1f376c7429c03c22
[3/7] arm64: dts: ti: k3-j721e-sk: Change timer nodes status to reserved
      commit: a8d1241bd6e57add2807c3127f987f8929bb45a1
[4/7] arm64: dts: ti: k3-j721s2-som-p0: Change timer nodes status to reserved
      commit: 1cf3a036f91a2e5a6187f7cea8f9bfab1d9b504f
[5/7] arm64: dts: ti: k3-am68-sk-som: Change timer nodes status to reserved
      commit: ce25e4c7dff5c9a392ad5a5c38c4fc7031305cd2
[6/7] arm64: dts: ti: k3-j784s4-evm: Change timer nodes status to reserved
      commit: d8087ca36a29fa81cc80dd0a9b347b2877cc9b3d
[7/7] arm64: dts: ti: k3-am69-sk: Change timer nodes status to reserved
      commit: bdebd509e43e508386488ba7a35cf714dffa0088

I dropped the fixes tag while applying: the behavior you are
considering here is firmware specific. While I understand it is
important for the board, the reported "fixes" tag has nothing to do
with the board, it is a SoC timer introduction which is not where the
bug is.

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