mpsl: flash sync: Treat simulated nrf54l15 like real one

Let's use the SOC_COMPATIBLE_NRF54LX kconfig option instead of SOC_SERIES_NRF54LX so we treat both the real and simulated targets equally. Signed-off-by: Alberto Escolar Piedras <[email protected]>
nrfconnect · Sep 6, 2024 · c965be5 · c965be5
1 parent 57dd360
commit c965be5
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/drivers/mpsl/flash_sync/flash_sync_mpsl.c b/drivers/mpsl/flash_sync/flash_sync_mpsl.c
@@ -56,7 +56,7 @@ static struct mpsl_context _context;
  */
 static uint32_t get_timeslot_time_us(void)
 {
-#ifdef CONFIG_SOC_SERIES_NRF54LX
+#ifdef CONFIG_SOC_COMPATIBLE_NRF54LX
 	nrf_timer_task_trigger(NRF_TIMER10, NRF_TIMER_TASK_CAPTURE0);
 	return nrf_timer_cc_get(NRF_TIMER10, NRF_TIMER_CC_CHANNEL0);
 #else
@@ -229,7 +229,7 @@ void nrf_flash_sync_get_timestamp_begin(void)
 
 bool nrf_flash_sync_check_time_limit(uint32_t iteration)
 {
-#ifdef CONFIG_SOC_SERIES_NRF54LX
+#ifdef CONFIG_SOC_COMPATIBLE_NRF54LX
 	/* The time taken in a previous write is not a predictor of the time taken
 	 * for the next write. Writing the same value as is already stored is much
 	 * faster than writing a different value. If the first few writes are fast