Re: [PATCH v9 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume

[Nishanth Menon]

Hi Markus Schneider-Pargmann (TI),

On Fri, 18 Sep 2026 11:17:44 +0200, Markus Schneider-Pargmann (TI) wrote:
> Split the firmware memory region in more specific parts so it is better
> described where which information is stored. Specifically the LPM metadata
> region is important as bootloader software like U-Boot has to know where
> that data is to be able to read that data and resume from RAM.
> 
> The bindings are already applied. The remaining patches use the new
> layout for the platforms that are capable to support IO+DDR. For IO+DDR
> the new layout is necessary as it defines the location of the LPM
> metadata.
> 
> [...]

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

[1/9] arm64: dts: ti: k3-am62a-phycore-som: Fix wkup R5F memory region size
      commit: 3690b591d07a2e8863eb96e2aff740da47b8de03
[2/9] arm64: dts: ti: k3-am62d2-evm: Fix wkup R5F memory region size
      commit: 5dd0e5b9d5f67276ff291f30da9bf5a17a46c48e
[3/9] arm64: dts: ti: k3-am62a7-sk: Fix wkup R5F memory region size
      commit: 8d36eb58c06b867f29a8df2f39f7fe6718c726af
[4/9] arm64: dts: ti: k3-am62p-verdin: Fix wkup R5F memory region size
      commit: 70c9859fcca8dd964a588a0642aed3bd71bc1dcd
[5/9] arm64: dts: ti: k3-am62p5-sk: Fix wkup R5F memory region size
      commit: 93cfb76923603ccaec3720dec065a7874458e67d
[6/9] arm64: dts: ti: var-som-am62p: Fix wkup R5F memory region size
      commit: c9b15cd49b3fbd54f3382655b4e898921a7adb4e
[7/9] arm64: dts: ti: k3-am62a: Split r5f memory region
      commit: 13aea49af974352c2a6a96608bbaa3ed3030706c
[8/9] arm64: dts: ti: k3-am62p: Split r5f memory region
      commit: 46b7261c2bad842e8b9a25106c132bb8ae83d634
[9/9] arm64: dts: ti: Add wkup R5F nodes to pre-ram bootphase
      commit: 0d14dd104de66eff1500dec9e80d72c4ab82b608

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