soc: st: stm32: use autogenerated compatible Kconfig macro variables

Instead of defining our own, use the DT_COMPAT_<> macro variables generated
by the build system inside the STM32 SoC Kconfig file.

Signed-off-by: Mathieu Choplain <[email protected]>

Author: mathieuchopstm

soc/st/stm32/Kconfig.defconfig

@@ -45,20 +45,16 @@ DT_ST_PRESCALER := st,prescaler
 DT_STM32_LPTIM_PATH := $(dt_nodelabel_path,stm32_lp_tick_source)
 
 DT_CHOSEN_Z_FLASH := zephyr,flash
-DT_COMPAT_XSPI := st,stm32-xspi
-DT_COMPAT_OSPI := st,stm32-ospi
-DT_COMPAT_QSPI := st,stm32-qspi
 
 DT_CHOSEN_FLASH_NODE := $(dt_chosen_path,$(DT_CHOSEN_Z_FLASH))
 DT_CHOSEN_FLASH_PARENT := $(dt_node_parent,$(DT_CHOSEN_FLASH_NODE))
-DT_FLASH_PARENT_IS_XSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_XSPI))
-DT_FLASH_PARENT_IS_OSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_OSPI))
-DT_FLASH_PARENT_IS_QSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_QSPI))
+DT_FLASH_PARENT_IS_XSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_ST_STM32_XSPI))
+DT_FLASH_PARENT_IS_OSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_ST_STM32_OSPI))
+DT_FLASH_PARENT_IS_QSPI := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_PARENT),$(DT_COMPAT_ST_STM32_QSPI))
 
 DT_CHOSEN_Z_FLASH_CTRL := zephyr,flash-controller
-DT_COMPAT_XSPI_NOR_CTRL := st,stm32-xspi-nor
 DT_CHOSEN_FLASH_CTRL_NODE := $(dt_chosen_path,$(DT_CHOSEN_Z_FLASH_CTRL))
-DT_FLASH_CTRL_IS_XSPI_NOR  := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_CTRL_NODE),$(DT_COMPAT_XSPI_NOR_CTRL))
+DT_FLASH_CTRL_IS_XSPI_NOR  := $(dt_node_has_compat,$(DT_CHOSEN_FLASH_CTRL_NODE),$(DT_COMPAT_ST_STM32_XSPI_NOR))
 
 config SYS_CLOCK_HW_CYCLES_PER_SEC
 	default "$(DT_STM32WB0_TIMER_FREQ)" if STM32WB0_RADIO_TIMER