From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: Nishanth Menon <nm@ti.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Dhruva Gole <d-gole@ti.com>,
Akashdeep Kaur <a-kaur@ti.com>,
Kevin Hilman <khilman@baylibre.com>,
Bjorn Andersson <andersson@kernel.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kendall Willis <k-willis@ti.com>,
devicetree@vger.kernel.org, Vishal Mahaveer <vishalm@ti.com>,
Sebin Francis <sebin.francis@ti.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/7] dt-bindings: remoteproc: k3-r5f: Split up memory regions
Date: Thu, 26 Mar 2026 09:53:23 -0500 [thread overview]
Message-ID: <177453680287.2360004.8754104483766299234.robh@kernel.org> (raw)
In-Reply-To: <20260318-topic-am62a-ioddr-dt-v6-19-v3-1-c41473cb23c3@baylibre.com>
On Wed, 18 Mar 2026 16:13:07 +0100, Markus Schneider-Pargmann (TI) wrote:
> Split up the region reserved for the firmware image in more specific
> sections to expose the full fixed layout. Especially the LPM metadata
> section is important for bootloaders as it contains information about
> how to exit IO+DDR. This is read by the bootloader but is written by the
> firmware.
>
> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
> ---
> .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 29 ++++++++++++++--------
> 1 file changed, 19 insertions(+), 10 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-03-26 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 15:13 [PATCH v3 0/7] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-18 15:13 ` [PATCH v3 1/7] dt-bindings: remoteproc: k3-r5f: Split up memory regions Markus Schneider-Pargmann (TI)
2026-03-26 14:53 ` Rob Herring (Arm) [this message]
2026-03-18 15:13 ` [PATCH v3 2/7] dt-bindings: remoteproc: k3-r5f: Add memory-region-names Markus Schneider-Pargmann (TI)
2026-03-26 14:53 ` Rob Herring (Arm)
2026-03-18 15:13 ` [PATCH v3 3/7] arm64: dts: ti: k3: Use memory-region-names for r5f Markus Schneider-Pargmann (TI)
2026-03-18 15:13 ` [PATCH v3 4/7] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-18 15:13 ` [PATCH v3 5/7] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-03-18 15:13 ` [PATCH v3 6/7] arm64: dts: ti: k3-am62a7-sk: Add r5f nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
2026-03-18 15:13 ` [PATCH v3 7/7] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-03-30 14:56 ` [PATCH v3 0/7] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Mathieu Poirier
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=177453680287.2360004.8754104483766299234.robh@kernel.org \
--to=robh@kernel.org \
--cc=a-kaur@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.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=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=sebin.francis@ti.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