Re: [PATCH v7 07/11] arm64: dts: ti: k3-am62a-ti-ipc-firmware: Move wkup reserved memory

"Markus Schneider-Pargmann" <[email protected]>
Newsgroups org.infradead.lists.linux-arm-kernel,dev.linux.lists.llvm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
Hi Andrew,

On Thu Jul 9, 2026 at 9:33 PM CEST, Andrew Davis wrote:
> On 7/1/26 7:39 AM, Markus Schneider-Pargmann (TI) wrote:
>> Move the reserved memory regions used for wkup_r5fss0_core0 to the
>> k3-am62a-ti-ipc-firmware.dtsi. These are all the same for the other
>> boards as well, so we can combine them here similar to what is already
>> done for the mcu_r5fss0_core0 memory regions.
>
> The reason we left this region here in the base DTSI is this region
> is for the DM firmware and is required for the SoC to function.
> The other firmware regions are all optional.

I left this in the base dts before and Nishanth pointed out that it
should be in the ipc-firmware.dtsi so it only needs to be changed in one
place:

  That was the entire purpose of splitting ipc-firmware.dtsi out -
  if the default firmware carveouts have changed, do the change in
  ipc-firmware.dtsi. That way some other firmware people will have could
  potentially have their own dtsi files and handle things appropriately
  there, even if they are using the same evm OR if they use the exact
  ipc-firmware on different boards, that will appropriately introduce
  the change there as well. BUT, do check first.

https://lore.kernel.org/r/20260507155710.5zch4ghhzrj7hnlh@immovably

Maybe I am misunderstanding what you are suggesting. Also note that the
memory-region list in wkup_r5fss0_core0 which references the memory
regions defined in the base dts were always in the ipc-firmware.dtsi.

Could you please help me understand how this is modeled so I can update
the patches appropriately?

Thanks!

Best
Markus
signature.asc (application/pgp-signature, 289 B)
-----BEGIN PGP SIGNATURE-----

iKMEABYKAEsWIQSJYVVm/x+5xmOiprOFwVZpkBVKUwUCao2N1RsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIRHG1zcEBiYXlsaWJyZS5jb20ACgkQhcFWaZAVSlMY
0wD+MW1P+fXLHbnT0Q5q0xRZNdlX5mzZrZjflYaQeXlZQVkBALnL4EjrbB40bxbu
e80zmZ+OmW/bF+SzGKpJy8SoyqYK
=pVaV
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.