drivers: clock_control: Update XTAL accuracy on nRF54L

We are not able to achive 50ppm on nRF54L. Working on fixing it propperly, but untill we do set what we get. (cherry picked from commit dbf62a5) Original-Signed-off-by: Martin Tverdal <[email protected]> GitOrigin-RevId: dbf62a5 Change-Id: I23435d6db4c0e4e0107ddcb2e8166da471556b24 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/5476005 Commit-Queue: Dawid Niedźwiecki <[email protected]> Tested-by: Dawid Niedźwiecki <[email protected]> Reviewed-by: Dawid Niedźwiecki <[email protected]> Tested-by: ChromeOS Prod (Robot) <[email protected]>
coreboot · Apr 23, 2024 · a0c45d6 · a0c45d6
1 parent 819b7ec
commit a0c45d6
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/drivers/clock_control/Kconfig.nrf b/drivers/clock_control/Kconfig.nrf
@@ -132,6 +132,7 @@ choice CLOCK_CONTROL_NRF_ACCURACY_PPM
 	prompt "32KHz clock accuracy"
 	default CLOCK_CONTROL_NRF_K32SRC_500PPM if CLOCK_CONTROL_NRF_K32SRC_RC && SOC_COMPATIBLE_NRF52X
 	default CLOCK_CONTROL_NRF_K32SRC_250PPM if CLOCK_CONTROL_NRF_K32SRC_RC
+	default CLOCK_CONTROL_NRF_K32SRC_150PPM if CLOCK_CONTROL_NRF_K32SRC_XTAL && SOC_SERIES_NRF54LX
 	default CLOCK_CONTROL_NRF_K32SRC_50PPM
 
 config CLOCK_CONTROL_NRF_K32SRC_500PPM