From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"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 v2 8/8] dt-bindings: remoteproc: k3-r5f: Require memory-region-names
Date: Fri, 13 Mar 2026 14:38:25 +0100 [thread overview]
Message-ID: <DH1P27ZP9QYQ.2IP3X8G218GR8@baylibre.com> (raw)
In-Reply-To: <20260313-quantum-modest-prawn-896bde@quoll>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Hi Krzysztof,
On Fri Mar 13, 2026 at 2:13 PM CET, Krzysztof Kozlowski wrote:
> On Thu, Mar 12, 2026 at 04:49:02PM +0100, Markus Schneider-Pargmann (TI) wrote:
>> If memory-region is used, require memory-region-names.
>
> Why?
This was a suggestion/comment from Conor in the last version:
Is this really optional? Shouldn't it be made mandatory so that it is
easy to tell the difference between the two configurations?
https://lore.kernel.org/all/20260303-hesitate-preoccupy-5e311cbd3e58@spud/
>
> I don't understand also why this is a separate change, but maybe answer
> to "Why are you doing it" would cover it as well.
I made this a separate patch so the git tree never has any
binding/devicectree warnings for memory-region-names even in-between
patches. That's why I created these patches in this order:
1. Add the memory-region-names as an optional property.
2. Add memory-region-names to all users of memory-region.
3. Make the property required if memory-region exists.
Best
Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-03-13 13:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:48 [PATCH v2 0/8] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-12 15:48 ` [PATCH v2 1/8] dt-bindings: remoteproc: k3-r5f: Split up memory regions Markus Schneider-Pargmann (TI)
2026-03-12 15:48 ` [PATCH v2 2/8] dt-bindings: remoteproc: k3-r5f: Add memory-region-names Markus Schneider-Pargmann (TI)
2026-03-12 15:48 ` [PATCH v2 3/8] arm64: dts: ti: k3-am62a7-sk: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-03-12 15:48 ` [PATCH v2 4/8] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-03-12 15:48 ` [PATCH v2 5/8] arm64: dts: ti: k3-am62a7-sk: Add r5f nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
2026-03-12 15:49 ` [PATCH v2 6/8] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-03-12 15:49 ` [PATCH v2 7/8] arm64: dts: ti: k3: Use memory-region-names for r5f Markus Schneider-Pargmann (TI)
2026-03-12 15:49 ` [PATCH v2 8/8] dt-bindings: remoteproc: k3-r5f: Require memory-region-names Markus Schneider-Pargmann (TI)
2026-03-13 13:13 ` Krzysztof Kozlowski
2026-03-13 13:38 ` Markus Schneider-Pargmann [this message]
2026-03-13 15:49 ` Krzysztof Kozlowski
2026-03-13 16:18 ` Conor Dooley
2026-03-14 14:28 ` Markus Schneider-Pargmann
2026-03-15 11:59 ` Conor Dooley
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=DH1P27ZP9QYQ.2IP3X8G218GR8@baylibre.com \
--to=msp@baylibre.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=krzk@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=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