[PATCH v2 3/4] arm: mack-k3: Kconfig: Add DM firmware reserved memory configs

[Francesco Dolcini]

On Thu, Jul 02, 2026 at 01:12:08PM -0500, Andrew Davis wrote:
> On 7/1/26 2:50 AM, Paresh Bhagat wrote:
> > Add Kconfig options for DM firmware reserved memory for K3 SOCs that
> > support DM firmware (K3_DM_FW enabled)
> > - K3_DM_FW_RESERVED_ADDR: DM firmware address
> > - K3_DM_FW_RESERVED_SIZE: DM firmware reserved size
> > 
> > These configs will be used to fixup the kernel device tree's reserved
> > memory node for DM. Currently the fixup is only done for AM62A7 SoC, as
> > K3_DM_FW_RESERVED_SIZE is being used to update DM reserved memory from
> > 0xf0000 to 0x1f0000 as the current reserved carveout is insufficient to
> > accommodate the binary.
> > 
> > For other platforms, the addresses and sizes are based on the existing
> > device tree reserved memory. If needed for other SoCs, address and size
> > could be modified in Kconfig.
> > 
> > Signed-off-by: Paresh Bhagat <p-bhagat at ti.com>
> > ---
> >   arch/arm/mach-k3/Kconfig | 21 +++++++++++++++++++++
> >   1 file changed, 21 insertions(+)
> > 
> > diff --git a/arch/arm/mach-k3/Kconfig b/arch/arm/mach-k3/Kconfig
> > index a32ed3a9683..1b6678e72b7 100644
> > --- a/arch/arm/mach-k3/Kconfig
> > +++ b/arch/arm/mach-k3/Kconfig
> > @@ -165,6 +165,27 @@ config K3_DM_FW
> >   	  bootloader, it makes RM and PM services not being available
> >   	  during R5 SPL execution time.
> > +config K3_DM_FW_RESERVED_ADDR
> > +	hex "Start address of DM firmware reserved memory region"
> > +	depends on !SOC_K3_AM642 && !SOC_K3_AM654
> > +	default 0x9c900000 if SOC_K3_AM62A7 || SOC_K3_AM62P5
> > +	default 0x9db00000 if SOC_K3_AM625
> > +	default 0xa0100000 if SOC_K3_J721E || SOC_K3_J7200 || SOC_K3_J721S2 || SOC_K3_J722S || SOC_K3_J784S4
> > +	help
> > +	  Start address of the DDR region reserved for DM firmware at runtime.
> > +	  Used only to fixup the kernel device-tree reserved-memory node.
> > +
> > +config K3_DM_FW_RESERVED_SIZE
> > +	hex "Reserved memory size for DM firmware"
> > +	depends on !SOC_K3_AM642 && !SOC_K3_AM654
> > +	default 0x1f00000 if SOC_K3_AM62A7
> > +	default 0xc00000 if SOC_K3_AM625
> > +	default 0x1e00000 if TARGET_VERDIN_AM62P_A53 || TARGET_VERDIN_AM62P_R5
> 
> Why is this one board different from the rest of the AM62P boards? I doubt
> the folks at Toradex have make a custom DM firmware, guessing they are just
> the first to notice our default DM firmware goes outside the current reserved
> memory size. This size likely needs to be made common for all AM62P.

You are right, we are not customizing anything on this regard.

Francesco