From: Paresh Bhagat <p-bhagat@ti.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>, <nm@ti.com>,
<vigneshr@ti.com>
Cc: <praneeth@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<v-singh1@ti.com>, <bb@ti.com>, <u-kumar1@ti.com>,
<anshuld@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: Rename DM firmware reserved memory nodes
Date: Fri, 3 Jul 2026 23:46:35 +0530 [thread overview]
Message-ID: <024b1d16-12a8-4d8a-9bc1-5061291a12f0@ti.com> (raw)
In-Reply-To: <DJN8XK5EIKU1.3FAVGBD6W2L2B@baylibre.com>
Hi Markus,
On 01/07/26 18:20, Markus Schneider-Pargmann wrote:
> Hi Paresh,
>
> On Tue Jun 30, 2026 at 5:09 PM CEST, Paresh Bhagat wrote:
>> Rename DM reserved memory nodes for K3 devices.
>>
>> Example:
>> memory@xxxxxxxx -> to dm@xxxxxxxx
>>
>> This allows U-Boot to identify and resize these regions using
>> fdt_fixup_reserved_memory() as done for TFA and optee.
> How will this work for the updated detailed layout bindings that got
> merged here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91ddd97e1bb26937a5c15fb51ec8f6b65dbe94b8
Thanks for pointing me to the binding update. Should have checked it
earlier.
>
> This splits up your one memory region into several memory regions. Here
> is one patch that uses that new memory region:
>
> https://lore.kernel.org/all/20260701-topic-am62a-ioddr-dt-v6-19-v7-9-e9db8b16821a@baylibre.com/
>
> This basically breaks up the one memory region into several regions.
> Wouldn't this break the fdt_fixup_reserved_memory() that you are trying
> to merge into u-boot and make this patch unnecessary?
Given that you are consolidating the memory regions and implementing the
new layout, I will wait for your series to be merged first.
>
> Best
> Markus
prev parent reply other threads:[~2026-07-03 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 15:09 [PATCH] arm64: dts: ti: Rename DM firmware reserved memory nodes Paresh Bhagat
2026-07-01 12:50 ` Markus Schneider-Pargmann
2026-07-03 18:16 ` Paresh Bhagat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=024b1d16-12a8-4d8a-9bc1-5061291a12f0@ti.com \
--to=p-bhagat@ti.com \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=v-singh1@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox