cmake/doc/samples/scripts/tests: Fix references to invalid Kconfigs

Fixes references to invalid Kconfigs

Signed-off-by: Jamie McCrae <[email protected]>

Author: nordicjm

cmake/sysbuild/partition_manager.cmake

@@ -539,7 +539,7 @@ foreach(d APP ${PM_DOMAINS})
     set(soc_nvs_controller_driver_kc CONFIG_SOC_FLASH_NRF_RRAM)
   elseif(${image_name}_CONFIG_SOC_SERIES_NRF71X)
     set(soc_nvs_controller mram_controller)
-    set(soc_nvs_controller_driver_kc CONFIG_SOC_FLASH_NRF_MRAMC)
+    set(soc_nvs_controller_driver_kc CONFIG_SOC_FLASH_NRF_MRAM)
   else()
     set(soc_nvs_controller flash_controller)
     set(soc_nvs_controller_driver_kc CONFIG_SOC_FLASH_NRF)

doc/nrf/libraries/caf/settings_loader.rst

@@ -48,7 +48,7 @@ After each module that sets a bit in the :c:func:`get_req_modules` function is i
 File system as settings backend
 ===============================
 
-If the settings backend is a file system (set with the :kconfig:option:`CONFIG_SETTINGS_FS` Kconfig option), make sure that the application mounts the file system before the Zephyr settings subsystem is initialized.
+If the settings backend is a file system (set with the :kconfig:option:`CONFIG_SETTINGS_FILE` Kconfig option), make sure that the application mounts the file system before the Zephyr settings subsystem is initialized.
 The CAF settings loader module calls the :c:func:`settings_subsys_init` initialization function during the system boot with the ``APPLICATION`` level and the initialization priority set by the :kconfig:option:`CONFIG_APPLICATION_INIT_PRIORITY` Kconfig option.
 
 Implementation details

samples/pmic/native/npm2100_fuel_gauge/README.rst

@@ -25,7 +25,21 @@ This sample allows the calculation of state of charge from a battery connected t
 
 Battery models for Alkaline AA (1S and 2S configuration), AAA (1S and 2S configuration), LR44, and Lithium-manganese dioxide coin cell CR2032 batteries are included.
 You can change the active battery model using a shell command, as illustrated in `Testing`_.
-You can also change the battery model at compile time using the :kconfig:option:`CONFIG_BATTERY_MODEL` Kconfig option.
+You can also change the battery model at compile time by selecting the type of battery via Kconfig:
+
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_ALKALINE_AA`    | Alkaline AA battery model                 |
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_ALKALINE_AAA`   | Alkaline AAA battery model                |
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_ALKALINE_2SAA`  | 2x alkaline AA battery (in series) model  |
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_ALKALINE_2SAAA` | 2x alkaline AAA battery (in series) model |
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_ALKALINE_LR44`  | Alkaline LR44 coin cell model             |
++-------------------------------------------------------+-------------------------------------------+
+| :kconfig:option:`CONFIG_BATTERY_MODEL_LITHIUM_CR2032` | Lithium CR2032 coin cell                  |
++-------------------------------------------------------+-------------------------------------------+
 
 .. _npm2100_fuel_gauge_wiring:
 

samples/zephyr/drivers/spi_flash/sample.yaml

@@ -17,7 +17,7 @@ common:
       - "Data read matches data written. Good!!"
 tests:
   sample.drivers.spi.flash.sqspi:
-    filter: CONFIG_MSPI_SQSPI and dt_compat_enabled("jedec,mspi-nor")
+    filter: CONFIG_MSPI_NRF_SQSPI and dt_compat_enabled("jedec,mspi-nor")
     platform_allow:
       - nrf54l15dk/nrf54l15/cpuapp
     integration_platforms:

scripts/partition_manager/partition_manager.rst

@@ -569,7 +569,7 @@ For external regions, ``DEFAULT_DRIVER_KCONFIG`` within :file:`partition_manager
 Out-of-tree drivers can select this value to attest that they provide support for the external flash.
 This is a hidden option and can be selected only by an external driver or a Kconfig option.
 
-This option is automatically set when :kconfig:option:`CONFIG_NRF_QSPI_NOR` or :kconfig:option:`CONFIG_SPI_NOR` is enabled.
+This option is automatically set when :kconfig:option:`CONFIG_NORDIC_QSPI_NOR` or :kconfig:option:`CONFIG_SPI_NOR` is enabled.
 If the application provides the driver in an unusual way, this option can be overridden by setting :kconfig:option:`CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK` in the application configuration.
 
 As partition manager does not know if partitions are used at runtime, consider the following:

tests/lib/pdn/CMakeLists.txt

@@ -28,4 +28,3 @@ add_compile_definitions(CONFIG_PDN_ESM_TIMEOUT=1000)
 add_compile_definitions(CONFIG_PDN_DEFAULTS_OVERRIDE)
 add_compile_definitions(CONFIG_PDN_DEFAULT_APN="apn0")
 add_compile_definitions(CONFIG_PDN_DEFAULT_FAM=2)
-add_compile_definitions(CONFIG_PDN_DYNAMIC_INFO_AT_BUF_SIZE=512)