From: Kendall Willis <k-willis@ti.com>
To: "Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
Judith Mendez <jm@ti.com>, Daniel Schultz <d.schultz@phytec.de>,
Andrew Davis <afd@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Paresh Bhagat <p-bhagat@ti.com>, Bryan Brattlof <bb@ti.com>,
Jai Luthra <jai.luthra@ideasonboard.com>,
Devarsh Thakkar <devarsht@ti.com>,
Beleswar Padhi <b-padhi@ti.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Stefano Radaelli <stefano.radaelli21@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Vishal Mahaveer <vishalm@ti.com>,
Kevin Hilman <khilman@baylibre.com>,
"Sebin Francis" <sebin.francis@ti.com>,
Akashdeep Kaur <a-kaur@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>, Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume
Date: Wed, 16 Sep 2026 15:52:36 -0500 [thread overview]
Message-ID: <20260916205236.hemdlwzjchmf6jm4@uda0506412> (raw)
In-Reply-To: <20260903-topic-am62a-ioddr-dt-v6-19-v8-0-74c650dfdea6@baylibre.com>
On 14:39-20260903, Markus Schneider-Pargmann (TI) wrote:
> Hi,
>
> 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.
>
> Additionally the two important devicetree nodes for resuming from IO+DDR
> have the bootph-pre-ram flag added as this data needs to be read before
> the RAM is in use.
>
> The changes in this series were suggested as part of the IO+DDR u-boot series:
> https://lore.kernel.org/r/814c211f-a9eb-4311-bb84-165b1a69755f@ti.com
>
> Note that concerns about uboot fixup of memory region fixups were
> discussed here:
> https://lore.kernel.org/r/DJD1Y3G9S1SP.2GHOZ5X4RYJFA@baylibre.com
>
> Best
> Markus
>
> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
For the series,
Reviewed-by: Kendall Willis <k-willis@ti.com>
Best,
Kendall
prev parent reply other threads:[~2026-09-16 20:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:39 [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 1/9] arm64: dts: ti: k3-am62a-phycore-som: Fix wkup R5F memory region size Markus Schneider-Pargmann (TI)
2026-09-03 14:52 ` Andrew Davis
2026-09-03 15:20 ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 2/9] arm64: dts: ti: k3-am62d2-evm: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 3/9] arm64: dts: ti: k3-am62a7-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 15:34 ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 4/9] arm64: dts: ti: k3-am62p-verdin: " Markus Schneider-Pargmann (TI)
2026-09-11 5:16 ` Francesco Dolcini
2026-09-03 12:39 ` [PATCH v8 5/9] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 6/9] arm64: dts: ti: var-som-am62p: " Markus Schneider-Pargmann (TI)
2026-09-11 12:00 ` Stefano Radaelli
2026-09-03 12:39 ` [PATCH v8 7/9] arm64: dts: ti: k3-am62a: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-09-03 12:55 ` sashiko-bot
2026-09-03 14:55 ` Markus Schneider-Pargmann
2026-09-03 12:39 ` [PATCH v8 8/9] arm64: dts: ti: k3-am62p: " Markus Schneider-Pargmann (TI)
2026-09-03 12:57 ` sashiko-bot
2026-09-04 7:35 ` Markus Schneider-Pargmann
2026-09-03 12:39 ` [PATCH v8 9/9] arm64: dts: ti: Add wkup R5F nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
2026-09-11 5:24 ` Francesco Dolcini
2026-09-16 10:17 ` Markus Schneider-Pargmann
2026-09-16 10:40 ` Francesco Dolcini
2026-09-16 16:07 ` Markus Schneider-Pargmann
2026-09-11 7:42 ` Nishanth Menon
2026-09-16 10:22 ` Markus Schneider-Pargmann
2026-09-11 2:07 ` [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume Bryan Brattlof
2026-09-16 20:52 ` Kendall Willis [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=20260916205236.hemdlwzjchmf6jm4@uda0506412 \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=afd@ti.com \
--cc=b-padhi@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d.schultz@phytec.de \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=hnagalla@ti.com \
--cc=jai.luthra@ideasonboard.com \
--cc=jm@ti.com \
--cc=justinstitt@google.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=msp@baylibre.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sebin.francis@ti.com \
--cc=stefano.radaelli21@gmail.com \
--cc=vigneshr@ti.com \
--cc=vishalm@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