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: <175766786790.25701.17214923767658263422.b4-ty@ti.com>
Date: Fri, 12 Sep 2025 04:49:58 -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>, <afd@...com>, <u-kumar1@...com>,
        <hnagalla@...com>, <jm@...com>, <d-gole@...com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        Robert Nelson
	<robertcnelson@...il.com>,
        Jo_o Paulo Gon_alves <joao.goncalves@...adex.com>,
        Parth Pancholi <parth.pancholi@...adex.com>,
        Emanuele Ghidoli
	<emanuele.ghidoli@...adex.com>,
        Francesco Dolcini
	<francesco.dolcini@...adex.com>,
        Matthias Schiffer
	<matthias.schiffer@...tq-group.com>,
        Logan Bristol
	<logan.bristol@...xas.edu>,
        Josua Mayer <josua@...id-run.com>, John Ma
	<jma@...tec.com>,
        Nathan Morrisson <nmorrisson@...tec.com>,
        Garrett Giordano
	<ggiordano@...tec.com>,
        Matt McKee <mmckee@...tec.com>, Wadim Egorov
	<w.egorov@...tec.de>,
        Andrejs Cainikovs <andrejs.cainikovs@...adex.com>,
        Max
 Krummenacher <max.krummenacher@...adex.com>,
        Stefan Eichenberger
	<stefan.eichenberger@...adex.com>,
        Hiago De Franco
	<hiago.franco@...adex.com>,
        Diogo Ivo <diogo.ivo@...mens.com>,
        Li Hua Qian
	<huaqian.li@...mens.com>,
        Jan Kiszka <jan.kiszka@...mens.com>,
        Baocheng Su
	<baocheng.su@...mens.com>,
        Benedikt Niedermayr
	<benedikt.niedermayr@...mens.com>
Subject: Re: [PATCH v4 00/34] Refactor TI IPC DT configs into dtsi

Hi Beleswar Padhi,

On Mon, 08 Sep 2025 19:57:52 +0530, Beleswar Padhi wrote:
> The TI K3 SoCs have multiple programmable remote processors like
> R5F, M4F, C6x/C7x etc. The TI SDKs for these SoCs offer sample firmware
> which could be run on these cores to demonstrate an "echo" IPC test.
> Those firmware require certain memory carveouts to be reserved from
> system memory, timers to be reserved, and certain mailbox
> configurations for interrupt based messaging. These configurations
> could be different for a different firmware.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
NOTE: I have'nt had feedback from Siemens team, but looking at the series,
things look fine overall. holler if a problem..
Thank you!

[01/34] arm64: dts: ti: k3-j7200: Enable R5F remote processors at board level
        commit: 7b09167cb7cb09282200903b6371996df4d76bc4
[02/34] arm64: dts: ti: k3-j721e: Enable remote processors at board level
        commit: 73d0df7437364feb1a39772eccbb4f1a604cf623
[03/34] arm64: dts: ti: k3-j721s2: Enable remote processors at board level
        commit: 368ae64a7188ac06d3cb2ee96975d40e6504e40d
[04/34] arm64: dts: ti: k3-j784s4-j742s2: Enable remote processors at board level
        commit: fa1b98ddfa1d44a98f70d7480c87f33f8d29c8d7
[05/34] arm64: dts: ti: k3-am62p-j722s: Enable remote processors at board level
        commit: ec158a0883c90528bbc1ec960a9b990d49a34099
[06/34] arm64: dts: ti: k3-am62: Enable remote processors at board level
        commit: bdc921171dbe13fdc41589d44217d560299bbd5c
[07/34] arm64: dts: ti: k3-am62a: Enable remote processors at board level
        commit: f927049553dfaa27acc099b21095ee488b199687
[08/34] arm64: dts: ti: k3-am64: Enable remote processors at board level
        commit: 93b4ff5b86e5bc53aeba3a0193597ba31a4e5839
[09/34] arm64: dts: ti: k3-am65: Enable remote processors at board level
        commit: c3fc9c1c1ac8f64ef333858ea42676889448a248
[10/34] arm64: dts: ti: k3-am62: Enable Mailbox nodes at the board level
        commit: bc590db1b5fe999d056ba66dc1990288c14f1ec3
[11/34] arm64: dts: ti: k3-am62a: Enable Mailbox nodes at the board level
        commit: 9ca8079eb36b71a86bb5851d9d3b7a49da8e595f
[12/34] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node
        commit: 4f1aee4723a796a92f17b23699dc861b582ddfd2
[13/34] arm64: dts: ti: k3: Rename rproc reserved-mem nodes to 'memory@...r'
        commit: aee0678597c63e5427e91b2e49a6c5ed4951f277
[14/34] arm64: dts: ti: k3-j721e-beagleboneai64: Add missing cfg for TI IPC FW
        commit: a564730142d5d23c197ca4b4741fb6a89e6f0c2c
[15/34] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware
        commit: fc4f6f0146d4c778859042a76b1e932b6334bf96
[16/34] arm64: dts: ti: k3-am62-verdin: Add missing cfg for TI IPC Firmware
        commit: a49f991e740f5f3917b4023705568aeb817ee773
[17/34] arm64: dts: ti: k3-am62-pocketbeagle2: Add missing cfg for TI IPC Firmware
        commit: 6104984a7d1d8c17c724e799501a1be2a2a35a52
[18/34] arm64: dts: ti: k3-am642-sr-som: Add missing cfg for TI IPC Firmware
        commit: e85524649959c2fa2477b66a450471df6e1fb725
[19/34] arm64: dts: ti: k3-am64-phycore-som: Add missing cfg for TI IPC Firmware
        commit: 67b98792407f41b369ecd799a4928db24dbb2058
[20/34] arm64: dts: ti: k3-am642-tqma64xxl: Add missing cfg for TI IPC Firmware
        commit: b13fb32f6bde4c0c533fab6e4bc240b75296e810
[21/34] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations"
        commit: 79a1778c7819c8491cdbdc1f7e46d478cb84d5cf
[22/34] Revert "arm64: dts: ti: k3-j721e-beagleboneai64: Fix reversed C6x carveout locations"
        commit: 932424a925ce79cbed0a93d36c5f1b69a0128de1
[23/34] arm64: dts: ti: k3-j721e-beagleboneai64: Switch MAIN R5F clusters to Split-mode
        commit: 897117c6bb4b151bd9326773cd6a5acdad4c47b4
[24/34] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: c5b645dbecd6d0b2689fa44eeefe2a2648172dc7
[25/34] arm64: dts: ti: k3-j721e-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 20ca55168b139c78d4e604a59dbc89403781ee0a
[26/34] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: e2581d3e0787a42f6ede8a15a66a93ae4a3ecd6f
[27/34] arm64: dts: ti: k3-j784s4-j742s2-ti-ipc-firmware-common: Refactor IPC cfg into new dtsi
        commit: 3dabfaa168d8b3835e210f90da3bf0f10b050fdb
[28/34] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 2742d963e1dd7f4a3d0505044323b091daffcddc
[29/34] arm64: dts: ti: k3-j722s-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 3cc04e49cd5d9c5af24eb4357775f35156b19fec
[30/34] arm64: dts: ti: k3-am62p-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 6bd0449be319a29096f3ee7cd415f8b6b28104c7
[31/34] arm64: dts: ti: k3-am62-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 1d6161617c10435e970d3bb3ef5de124b94fe719
[32/34] arm64: dts: ti: k3-am62a-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: d4ab4a33c8e0a8cd33c8cb70ba3c74dba770c2a4
[33/34] arm64: dts: ti: k3-am64-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: 3ad3ab0bfa577d1f93e7048224c267b32ed4d6a1
[34/34] arm64: dts: ti: k3-am65-ti-ipc-firmware: Refactor IPC cfg into new dtsi
        commit: a26bc9175f679da37ee3a52669aeb26db7f57738

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
https://ti.com/opensource


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ