On 06/08/2025 14:36, Patrice CHOTARD wrote:
Signed-off-by: Patrice Chotard patrice.chotard@foss.st.com
arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 1 + 1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts b/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts index 2f561ad4066544445e93db78557bc4be1c27095a..16309029758cf24834f406f5203046ded371a8f9 100644 --- a/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts +++ b/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts @@ -197,6 +197,7 @@ &i2c8 { &ommanager { memory-region = <&mm_ospi1>;
- memory-region-names = "mm_ospi1";
It does not look like you tested the DTS against bindings. Please run `make dtbs_check W=1` (see
My bad, i am preparing the v2.
Why? I claim this is not needed according to your description. You said it is necessary to identify "memory-map area's configuration." but memory-region already tells that. What exactly is not identified?
Best regards, Krzysztof