soc: nrf: Use data from DTS to populate HAS_HW_NRF_* Kconfig options
Instead of selecting appropriate HAS_HW_NRF_* options for particular nRF SoCs (and simulated nRF52 target), set their values basing on information from devicetree. Correct also semantics of those options so that they are set only when a corresponding DT node is enabled. This allows using them directly in Kconfig dependencies of Zephyr drivers for nRF peripherals. Update appropriately these dependencies. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
This commit is contained in:
parent
f80e572750
commit
586e26e8fc
18 changed files with 178 additions and 837 deletions
|
@ -10,19 +10,6 @@ config BOARD_NRF52_BSIM
|
|||
select CONSOLE_HAS_DRIVER
|
||||
select NRF_RTC_TIMER
|
||||
select CLOCK_CONTROL
|
||||
# Indicate that the nRF RNG peripheral is present (actually a model
|
||||
# of it), so that the corresponding driver becomes available (see
|
||||
# dependencies of the ENTROPY_NRF5_RNG option).
|
||||
select HAS_HW_NRF_RNG
|
||||
# Indicate that CCM supports 8 bit length field, to support full
|
||||
# length LL PDUs.
|
||||
select HAS_HW_NRF_CCM_LFLEN_8BIT
|
||||
# Indicate 2M support so that Phy procedure can be enabled.
|
||||
select HAS_HW_NRF_RADIO_BLE_2M
|
||||
# Do the same for the CLOCK and POWER peripherals, so that the nrfx
|
||||
# drivers for them can be used.
|
||||
select HAS_HW_NRF_CLOCK
|
||||
select HAS_HW_NRF_POWER
|
||||
select HAS_NRFX
|
||||
help
|
||||
Will produce a console Linux process which can be executed natively.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue