On Thu, 15 Oct 2026 10:39:22 -0400, [email protected] wrote: > From: Laurentiu Mihalcea <[email protected]> > > Document the optional memory-region-names property. > > The driver currently derives the memory region type from the referenced > memory node name, creating a hidden DT ABI. Since memory node names are > not constrained by the binding, incorrect names can silently pass DT > validation, as seen in examples using "vdevbuffer" instead of > "vdev0buffer" ([1] and [2]). > > Add memory-region-names to explicitly identify the expected memory regions > and avoid relying on memory node names as ABI. > > Link: > https://lore.kernel.org/imx/[email protected]/ > [1] > Link: > https://lore.kernel.org/imx/alexXTYQHUs76J7v@SMW015318/T/#mb9dc709ff3adc24d9db6d30c973f37b580f6f1f9 > [2] > Signed-off-by: Laurentiu Mihalcea <[email protected]> > Signed-off-by: Frank Li <[email protected]> > --- > Use optional property to keep back compatible with old platform. > New platform should use memory-region-names. > --- > .../devicetree/bindings/remoteproc/fsl,imx-rproc.yaml | 11 > +++++++++++ > 1 file changed, 11 insertions(+) >
Reviewed-by: Rob Herring (Arm) <[email protected]>
