linux-kernel - Re: [PATCH v5 0/2] Add Remoteproc Support for TI's J722S 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: <172522532253.1011545.14727446934564211822.b4-ty@ti.com>
Date: Sun, 1 Sep 2024 16:15:37 -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>, <j-choudhary@...com>,
        <vaishnav.a@...com>, <afd@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5 0/2] Add Remoteproc Support for TI's J722S SoCs

Hi Beleswar Padhi,

On Fri, 30 Aug 2024 21:47:40 +0530, Beleswar Padhi wrote:
> The K3 J722S SoCs have one single-core Arm Cortex-R5F processor in each
> of the WAKEUP, MCU and MAIN voltage domain, and two C71x DSP subsystems
> in MAIN voltage domain. Thus, this series adds the DT Nodes for the
> remote processors to add support for IPC.
> 
> This series also enables IPC on the J722S-EVM platform based on the
> above SoC by adding the mailbox instances, shared memory carveouts and
> reserving the conflicting timer nodes (as they are used by remoteproc
> firmware).
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j722s-main: Add R5F and C7x remote processor nodes
      commit: 05b1653c4fc148189743e4b3cbef798e49db61f0
[2/2] arm64: dts: ti: k3-j722s-evm: Enable Inter-Processor Communication
      commit: 5b035d14a508efd065895607ae7a6f913b26fef8

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