From: Conor Dooley <conor@kernel.org>
To: "Markus Schneider-Pargmann (TI)" <msp@baylibre.com>
Cc: Nishanth Menon <nm@ti.com>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Mathieu Poirier <mathieu.poirier@linaro.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>,
Tero Kristo <kristo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/6] dt-bindings: remoteproc: k3-r5f: Add memory-region-names
Date: Tue, 3 Mar 2026 18:31:56 +0000 [thread overview]
Message-ID: <20260303-hesitate-preoccupy-5e311cbd3e58@spud> (raw)
In-Reply-To: <20260303-topic-am62a-ioddr-dt-v6-19-v1-2-12fe72bb40d2@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Tue, Mar 03, 2026 at 04:13:00PM +0100, Markus Schneider-Pargmann (TI) wrote:
> Add names to the memory-region-names for easier idenfitication of memory
> regions.
>
> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
> ---
> .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
> index 6aadc61e20f9f4c27f5b9c87ab2025a02776c5de..76ef23afe8c9f7f155dfec7fcabc7c60b8b286c6 100644
> --- a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
> @@ -182,6 +182,25 @@ patternProperties:
> - description: DM RM/PM trace and firmware code/data
> additionalItems: true
>
> + memory-region-names:
> + description: |
> + Optional names for the memory regions specified in the memory-region
Is this really optional? Shouldn't it be made mandatory so that it is
easy to tell the difference between the two configurations?
> + property.
> + oneOf:
> + - description: Basic configuration with DMA and firmware regions
> + items:
> + - const: dma
> + - const: firmware
> +
> + - description: Extended LPM configuration with split memory regions
> + items:
> + - const: dma
> + - const: ipc
> + - const: lpm-stub
> + - const: lpm-metadata
> + - const: lpm-context
> + - const: dm-firmware
> +
> # Optional properties:
> # --------------------
> # The following properties are optional properties for each of the R5F cores:
>
> --
> 2.51.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-03-03 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:12 [PATCH 0/6] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-03 15:12 ` [PATCH 1/6] dt-bindings: remoteproc: k3-r5f: Split up memory regions Markus Schneider-Pargmann (TI)
2026-03-03 15:13 ` [PATCH 2/6] dt-bindings: remoteproc: k3-r5f: Add memory-region-names Markus Schneider-Pargmann (TI)
2026-03-03 18:31 ` Conor Dooley [this message]
2026-03-03 18:33 ` Conor Dooley
2026-03-04 13:38 ` Markus Schneider-Pargmann
2026-03-03 15:13 ` [PATCH 3/6] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-03 15:13 ` [PATCH 4/6] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-03-03 15:13 ` [PATCH 5/6] arm64: dts: ti: k3-am62a7-sk: Add r5f nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
2026-03-03 15:13 ` [PATCH 6/6] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
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=20260303-hesitate-preoccupy-5e311cbd3e58@spud \
--to=conor@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=robh@kernel.org \
--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