OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/flash/Kconfig.nrf

37 lines
961 B
Plaintext
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
drivers: nrf: add support for forcing driver implementation An external project extending the Zephyr RTOS and its drivers may have subsystems that must use its own specific driver(s) when active. One example is the nRF5x NVMC that must be scheduled in between radio operations. A subsystem may also be dependent on its own drivers for security, real-time and/or because of hardware constrains. In order to not introduce non-Zephyr specific code into the Zephyr tree, an option is added to disable the in-tree drivers in Zephyr. Because Kconfig does not support a good way of de-selecting other symbols, a variable on the form `<DRIVER>_FORCE_ALT` is added as a dependency for each `<DRIVER>`. For example, the out-of-tree subsystem will select `FLASH_NRF_FORCE_ALT` to disable the in-tree driver. A solution for issue #8181 would open up for a more general solution, however #8181 requires significant effort. Support for out-of-tree drivers is added to Nordic drivers for clock_control, entropy and flash. A generic solution for this is desired. Issue #14527 is tracking that progress. Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
2019-02-21 23:02:16 +08:00
config FLASH_NRF_FORCE_ALT
bool
depends on SOC_COMPATIBLE_NRF
help
This option can be enabled to force an alternative implementation
of the flash driver.
if !FLASH_NRF_FORCE_ALT
kconfig: flash: Move nrf code into it's own file Cleanup the Kconfig code for the flash driver. Platform-specific options should be in their own Kconfig files to be consistent and to not pollute the common configuration. To this end we move the nrf options into it's own file. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-02-15 21:45:52 +08:00
config SOC_FLASH_NRF
bool "Nordic Semiconductor nRF flash driver"
depends on SOC_FAMILY_NRF
select FLASH_HAS_PAGE_LAYOUT
select FLASH_HAS_DRIVER_ENABLED
drives/flash: use nrfx for nrf Introduce nrfx_nvmc driver into nordic flash driver implementation. Thanks to that nrf9160 SoC becomes supported by the driver. nrfx helps dealing with differences with interface to the NVMC in secure and non-secure execution modes. This patch adds NRFX_NVMC Kconfig entry for enabling nrfx_nvmc and select it along with nordic flash driver. Disabled UICR operation on nRF9160 for non-secure build as UICR is not available in this mode. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2019-04-01 23:26:05 +08:00
select NRFX_NVMC
drivers: nrf5: Don't force specific drivers from soc/arm/nordic_nrf Redefining the config will not let another (out-of-source) driver be chosen instead of the default. The driver is practically forced by the soc settings. This commit moves default settings from soc/arm/nordic_nrf into the drivers themselves. Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
2019-02-21 22:53:29 +08:00
default y
kconfig: flash: Move nrf code into it's own file Cleanup the Kconfig code for the flash driver. Platform-specific options should be in their own Kconfig files to be consistent and to not pollute the common configuration. To this end we move the nrf options into it's own file. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-02-15 21:45:52 +08:00
help
Enables Nordic Semiconductor nRF flash driver.
config SOC_FLASH_NRF_RADIO_SYNC
bool "Nordic nRFx flash driver synchronized with radio"
depends on SOC_FLASH_NRF && BT_CTLR
default y
help
Enable synchronization between flash memory driver and radio.
config SOC_FLASH_NRF_UICR
bool "Access to UICR"
drives/flash: use nrfx for nrf Introduce nrfx_nvmc driver into nordic flash driver implementation. Thanks to that nrf9160 SoC becomes supported by the driver. nrfx helps dealing with differences with interface to the NVMC in secure and non-secure execution modes. This patch adds NRFX_NVMC Kconfig entry for enabling nrfx_nvmc and select it along with nordic flash driver. Disabled UICR operation on nRF9160 for non-secure build as UICR is not available in this mode. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2019-04-01 23:26:05 +08:00
depends on SOC_FLASH_NRF && !TRUSTED_EXECUTION_NONSECURE
kconfig: flash: Move nrf code into it's own file Cleanup the Kconfig code for the flash driver. Platform-specific options should be in their own Kconfig files to be consistent and to not pollute the common configuration. To this end we move the nrf options into it's own file. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-02-15 21:45:52 +08:00
help
Enable operations on UICR. Once enabled UICR are written or read as
ordinary flash memory. Erase is possible for whole UICR at once.
drivers: nrf: add support for forcing driver implementation An external project extending the Zephyr RTOS and its drivers may have subsystems that must use its own specific driver(s) when active. One example is the nRF5x NVMC that must be scheduled in between radio operations. A subsystem may also be dependent on its own drivers for security, real-time and/or because of hardware constrains. In order to not introduce non-Zephyr specific code into the Zephyr tree, an option is added to disable the in-tree drivers in Zephyr. Because Kconfig does not support a good way of de-selecting other symbols, a variable on the form `<DRIVER>_FORCE_ALT` is added as a dependency for each `<DRIVER>`. For example, the out-of-tree subsystem will select `FLASH_NRF_FORCE_ALT` to disable the in-tree driver. A solution for issue #8181 would open up for a more general solution, however #8181 requires significant effort. Support for out-of-tree drivers is added to Nordic drivers for clock_control, entropy and flash. A generic solution for this is desired. Issue #14527 is tracking that progress. Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
2019-02-21 23:02:16 +08:00
endif #!FLASH_NRF_FORCE_ALT