dts: bindings: flash: stm32-qspi-nor: inlcude soc-nv-flash binding

Many Zephyr subsystems as well MCUboot rely on the write-block-size and
erase-block-size properties, of the chosen Flash device in DT,
to determine the optimal parameters for using the flash & its partitions.

Include the soc-nv-flash binding in STM32 External NOR Flash binding so
that those two properties can be specified in the external Flash node
in board DT.

Until now, the workaround for STM32 boards using MCUboot has been to
disable CONFIG_BOOT_MAX_IMG_SECTORS_AUTO in MCUboot's board extra conf
and to set CONFIG_BOOT_MAX_IMG_SECTORS manually depending on the app slot
size & the NOR Flash sector size.

Signed-off-by: Abderrahmane JARMOUNI <[email protected]>

Author: JarmouniA

dts/bindings/flash_controller/st,stm32-qspi-nor.yaml

@@ -19,7 +19,7 @@ description: |
 
 compatible: "st,stm32-qspi-nor"
 
-include: ["flash-controller.yaml", "jedec,jesd216.yaml"]
+include: ["flash-controller.yaml", "jedec,jesd216.yaml", "soc-nv-flash.yaml"]
 
 on-bus: qspi