Re: [PATCH v3 0/4] Add SRAM Nodes for VPU

[Nishanth Menon]

Hi Brandon Brnich,

On Mon, 21 Sep 2026 13:48:46 -0500, Brandon Brnich wrote:
> This series is responsible for adding the SRAM nodes for the Wave5 VPU to
> use. First patch is responsible for carving out the SRAM pool from
> main_navss that the VPU on J721s2 will then reference.
> 
> The last 2 patches use the existing oc_sram pool already found in the
> relevant device trees.
> 
> [...]

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

[1/4] arm64: dts: ti: k3-j721s2-main: Add mmio-sram node to main_navss
      commit: b4824bac766e1696a31c54c14541b65e33eb683f
[2/4] arm64: dts: ti: k3-j721s2-main: Assign SRAM to VPU node
      commit: 86ab93a198114653faf0fef11a88d4a240f5adf4
[3/4] arm64: dts: ti: k3-am62a-main: Assign SRAM to VPU node
      commit: 0bd8ecba297bd50fe5b154a96f6eaf0233b28dd3
[4/4] arm64: dts: ti: k3-am62p-j722s-common-main: Assign SRAM to VPU node
      commit: 330236fda4fd7a63e3bf9d9ce1b7ce227ddb8f1c

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