From: Vignesh Raghavendra <vigneshr@ti.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, "Suman Anna" <s-anna@ti.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
"Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: Vishal Mahaveer <vishalm@ti.com>,
Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
Sebin Francis <sebin.francis@ti.com>,
"Kendall Willis" <k-willis@ti.com>,
Akashdeep Kaur <a-kaur@ti.com>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: (subset) [PATCH v3 0/7] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region
Date: Sat, 11 Apr 2026 20:17:41 +0530 [thread overview]
Message-ID: <177591886114.88632.3713559346133832075.b4-ty@b4> (raw)
In-Reply-To: <20260318-topic-am62a-ioddr-dt-v6-19-v3-0-c41473cb23c3@baylibre.com>
Hi Markus Schneider-Pargmann (TI),
On Wed, 18 Mar 2026 16:13:06 +0100, Markus Schneider-Pargmann (TI) wrote:
> arm64: dts: ti: k3-am62a7-sk: Split r5f memory region
>
> 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.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[3/7] arm64: dts: ti: k3: Use memory-region-names for r5f
commit: 8fcd12e26db9e9b2128f0d813972f76a9c846eef
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh
prev parent reply other threads:[~2026-04-11 14:48 UTC|newest]
Thread overview: 19+ 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)
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-04-10 4:30 ` Vignesh Raghavendra
2026-04-10 13:42 ` Markus Schneider-Pargmann
2026-04-11 14:47 ` Vignesh Raghavendra
2026-04-13 14:58 ` Markus Schneider-Pargmann
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
2026-04-08 15:03 ` Rob Herring
2026-04-09 9:46 ` Vignesh Raghavendra
2026-04-10 13:54 ` Markus Schneider-Pargmann
2026-04-11 14:47 ` Vignesh Raghavendra [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=177591886114.88632.3713559346133832075.b4-ty@b4 \
--to=vigneshr@ti.com \
--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=robh@kernel.org \
--cc=s-anna@ti.com \
--cc=sebin.francis@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