tests: benchmarks: multicore: Cleanup Global Domain Freq. switching

Remove Kconfigs related to global domain frequency switching.
There were significant changes to GDF switching.

Signed-off-by: Sebastian Głąb <[email protected]>

Author: nordic-segl

tests/benchmarks/multicore/common/remote_gdf_switching/CMakeLists.txt

@@ -12,8 +12,4 @@ config TEST_SLEEP_DURATION_MS
 	  Based on the value of 'min-residency-us' specified for each power state defined in the DTS,
 	  core enters the lowest possible power state.
 
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_SWITCHING
-	bool "Enable global domain frequency changing"
-	select CLOCK_CONTROL
-
 source "Kconfig.zephyr"

tests/benchmarks/multicore/common/remote_gdf_switching/boards/nrf54h20dk_nrf54h20_cpurad.overlay

@@ -19,8 +19,4 @@ config TEST_ROLE_REMOTE
 	  KConfig used in synchronization phase.
 	  Set TEST_ROLE_REMOTE=y on core that shall synchronize with the Host core.
 
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_SWITCHING
-	bool "Enable global domain frequency changing from remote"
-	select CLOCK_CONTROL
-
 source "Kconfig.zephyr"

tests/benchmarks/multicore/common/remote_gdf_switching/prj.conf

@@ -12,32 +12,4 @@ config TEST_SLEEP_DURATION_MS
 	  Based on the value of 'min-residency-us' specified for each power state defined in the DTS,
 	  core enters the lowest possible power state.
 
-choice GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION
-	prompt "Global domain clock frequency"
-	default GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-	bool "320MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_256MHZ
-	bool "256MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_128MHZ
-	bool "128MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_64MHZ
-	bool "64MHz"
-
-endchoice
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_MHZ
-	int
-	default 320 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-	default 256 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_256MHZ
-	default 128 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_128MHZ
-	default 64 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_64MHZ
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_SWITCHING
-	bool "Enable global domain frequency changing when driver is active"
-
 source "Kconfig.zephyr"

tests/benchmarks/multicore/common/remote_gdf_switching/src/main.c

@@ -5,11 +5,7 @@
 #
 
 if(SB_CONFIG_SOC_NRF54H20)
-  if(SB_CONFIG_REMOTE_GLOBAL_DOMAIN_CLOCK_FREQUENCY_SWITCHING)
-    set(REMOTE_SOURCE_DIR ${ZEPHYR_NRF_MODULE_DIR}/tests/benchmarks/multicore/common/remote_gdf_switching)
-  else()
-    set(REMOTE_SOURCE_DIR ${APP_DIR}/remote)
-  endif()
+  set(REMOTE_SOURCE_DIR ${APP_DIR}/remote)
 
   # Add remote project
   ExternalZephyrProject_Add(

tests/benchmarks/multicore/idle_counter/Kconfig

@@ -45,32 +45,4 @@ config TEST_SPI_RELEASE_BEFORE_SLEEP
 	  first test iteration will see SPI CS signal activation. Next test iterations
 	  will NOT observe changes on SPI CS signal.
 
-choice GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION
-	prompt "Global domain clock frequency"
-	default GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-	bool "320MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_256MHZ
-	bool "256MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_128MHZ
-	bool "128MHz"
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_64MHZ
-	bool "64MHz"
-
-endchoice
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_MHZ
-	int
-	default 320 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_320MHZ
-	default 256 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_256MHZ
-	default 128 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_128MHZ
-	default 64 if GLOBAL_DOMAIN_CLOCK_FREQUENCY_OPTION_64MHZ
-
-config GLOBAL_DOMAIN_CLOCK_FREQUENCY_SWITCHING
-	bool "Enable global domain frequency changing when driver is active"
-
 source "Kconfig.zephyr"