From a0c45d6a20fb8ebda2fff33bc130d9642e195851 Mon Sep 17 00:00:00 2001 From: Martin Tverdal Date: Mon, 22 Apr 2024 13:44:04 +0200 Subject: [PATCH] drivers: clock_control: Update XTAL accuracy on nRF54L MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 dbf62a5a2a84edfe3fce4d6dc3524d3e18dea59c) Original-Signed-off-by: Martin Tverdal GitOrigin-RevId: dbf62a5a2a84edfe3fce4d6dc3524d3e18dea59c Change-Id: I23435d6db4c0e4e0107ddcb2e8166da471556b24 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/5476005 Commit-Queue: Dawid Niedźwiecki Tested-by: Dawid Niedźwiecki Reviewed-by: Dawid Niedźwiecki Tested-by: ChromeOS Prod (Robot) --- drivers/clock_control/Kconfig.nrf | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clock_control/Kconfig.nrf b/drivers/clock_control/Kconfig.nrf index 8b30772f26c..725a7694986 100644 --- 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