diff options
| author | Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com> | 2026-10-23 15:52:50 -0400 |
|---|---|---|
| committer | Mathieu Poirier <mathieu.poirier@linaro.org> | 2026-11-02 11:46:40 -0600 |
| commit | 8396089f91fa07dd77b580e045334e670f782ff8 (patch) | |
| tree | 3ccb181c11aba895b920ebeab3c0682d305464d4 /scripts/Makefile.thinlto | |
| parent | ebb21cc5d1c0950a8cb35f5f2870593f97724973 (diff) | |
| download | linux-next-8396089f91fa07dd77b580e045334e670f782ff8.tar.gz linux-next-8396089f91fa07dd77b580e045334e670f782ff8.zip | |
remoteproc: imx_rpoc: Use memory-region-names to avoid implicit ABI
The driver currently derives the memory region type from the referenced
memory node name, creating a implicit 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]).
Parse memory-region-names to identify the expected memory regions and avoid
relying on memory node names as ABI.
Link: https://lore.kernel.org/imx/a3602ef8-2b77-4cc3-adef-2c4cba08a5d9@nabladev.com/ [1]
Link: https://lore.kernel.org/imx/alexXTYQHUs76J7v@SMW015318/T/#mb9dc709ff3adc24d9db6d30c973f37b580f6f1f9 [2]
Signed-off-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Francesco Valla <francesco@valla.it>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
Link: https://lore.kernel.org/r/20261023-memory-region-name-v9-2-ad597887dfe9@nxp.com
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
