mpsl: Add KConfig around forcing RRAM when running from NONSECURE

Since this isn't makes powerconsumption be very high,
we can let it only be done when "advanced" bluetotoh features are used.

Signed-off-by: Martin Tverdal <[email protected]>

Author: martintv

subsys/mpsl/init/Kconfig

@@ -119,6 +119,15 @@ config MPSL_INIT_PRIORITY
 	  must be lower than CONFIG_NRFS_BACKEND_IPC_SERVICE_INIT_PRIO. The nrf2 clock control depends
 	  on the nRFS backend.
 
+config MPSL_FORCE_RRAM_ON_ALL_THE_TIME
+	bool "Force RRAM to stay on"
+	depends on TRUSTED_EXECUTION_NONSECURE
+	default y
+	help
+	  This option forces RRAM to stay on.
+	  This is not needed when only basic bluetooth features are used.
+	  Only needed when for example LLPM, Frame space update, ISO or Channel Sounding is used.
+
 module=MPSL
 module-str=MPSL
 source "$(ZEPHYR_BASE)/subsys/logging/Kconfig.template.log_config"

subsys/mpsl/init/mpsl_init.c

@@ -445,10 +445,8 @@ static int32_t mpsl_lib_init_internal(void)
 		return err;
 	}
 #endif /* MPSL_TIMESLOT_SESSION_COUNT > 0 */
-#if defined(NRF_TRUSTZONE_NONSECURE)
-	/* Temporary fix in order to get mpsl to work well when
-	 *  compiling for nrf54l15dk/nrf54l15/cpuapp/ns
-	 */
+#if defined(NRF_TRUSTZONE_NONSECURE) && \
+	defined(CONFIG_MPSL_FORCE_RRAM_ON_ALL_THE_TIME)
 	uint32_t result_out;
 	uint32_t result = tfm_platform_mem_write32((uint32_t)&NRF_RRAMC_S->POWER.LOWPOWERCONFIG,
 		RRAMC_POWER_LOWPOWERCONFIG_MODE_Standby << RRAMC_POWER_LOWPOWERCONFIG_MODE_Pos,