soc: adi: Add config flag to manage tf-m hal_adi repository

Add configuration flag to manage tf-m hal_adi repository during build
hal_adi can be used either over zephyr or download during build

Signed-off-by: Sadik Ozer <[email protected]>

Author: ozersa

modules/trusted-firmware-m/CMakeLists.txt

@@ -246,6 +246,11 @@ if (CONFIG_BUILD_WITH_TFM)
     list(APPEND TFM_CMAKE_ARGS -DTFM_PLATFORM_NXP_HAL_FILE_PATH=${TFM_PLATFORM_NXP_HAL_FILE_PATH})
   endif()
 
+  if(CONFIG_BOARD_MAX32657EVKIT_MAX32657_NS AND CONFIG_TFM_HAL_ADI_PATH_LOCAL)
+    # Supply path to hal_adi for TF-M build
+    list(APPEND TFM_CMAKE_ARGS -DHAL_ADI_PATH=${ZEPHYR_ADI_MODULE_DIR})
+  endif()
+
   if(CONFIG_TFM_BL2 AND CONFIG_TFM_MCUBOOT_PATH_LOCAL)
     # Supply path to MCUboot for TF-M build
     list(APPEND TFM_CMAKE_ARGS -DMCUBOOT_PATH=${ZEPHYR_MCUBOOT_MODULE_DIR})

soc/adi/max32/Kconfig

@@ -73,4 +73,29 @@ config BUILD_WITH_TFM
 	help
 	  Auto set WITH_TFM for a Non-Secure version of the board,
 
+choice TFM_HAL_ADI_PATH
+	prompt "Path to hal_adi or DOWNLOAD to fetch automatically"
+	default TFM_HAL_ADI_PATH_LOCAL
+	help
+	   Path to hal_adi for TF-M builds. The default option
+	   is to use Zephyr hal_adi module. As an alternative,
+	   users may switch to the 'download' version; in that
+	   case hal_adi will be fetched by the TF-M build during
+	   build time. The default option ensures that Zephyr builds
+	   with TF-M do not fetch external trees.
+
+config TFM_HAL_ADI_PATH_LOCAL
+	bool "TF-M to use Zephyr hal_adi"
+	help
+	  TF-M builds will use the Zephyr hal_adi version,
+	  which is present in the hal_adi module.
+
+config TFM_HAL_ADI_PATH_DOWNLOAD
+	bool "TF-M to automatically download hal_adi during build"
+	help
+	  TF-M builds will let the TF-M build to automatically
+	  fetch and check-out the hal_adi version to use in the build.
+
+endchoice
+
 endif # SOC_FAMILY_MAX32