Re: [PATCH v3 1/4] dt-bindings: remoteproc: imx_rproc: document optional "memory-region-names"

[Krzysztof Kozlowski <krzk@kernel.org>]

On 31/07/2026 11:37, Krzysztof Kozlowski wrote:
> On Thu, Jul 30, 2026 at 09:34:09AM -0700, Laurentiu Mihalcea wrote:
>> From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>>
>> The carveout region names are derived based on the DT node names. Because
>> of this, the DT node names are ABI, which is not supposed to happen.
>>
>> Fix this by documenting an additional, optional property:
>> "memory-region-names". This way, the software will have a way to build the
>> carveout region names without relying on the DT node names.
> 
> That's not the point of xxx-names property. It only serves as a helper
> to get the resource.
> 
>>
>> Signed-off-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>> ---
>>  .../devicetree/bindings/remoteproc/fsl,imx-rproc.yaml         | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> index c18f71b64889..8e3e6676a95e 100644
>> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> @@ -62,6 +62,10 @@ properties:
>>      minItems: 1
>>      maxItems: 32
>>  
>> +  memory-region-names:
>> +    minItems: 1
>> +    maxItems: 32
> 
> This cannot be flexible and unspecific. Why "yellow submarine" would be
> a correct name?
> 

And I already SAID that at v2, so you just keep pushing this without
implementing feedback.

NAK

Best regards,
Krzysztof