586e26e8fc
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>
14 lines
480 B
Text
14 lines
480 B
Text
# NRF AES ECB configuration options
|
|
|
|
# Copyright (c) 2020 Nordic Semiconductor ASA
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
config CRYPTO_NRF_ECB
|
|
bool "nRF AES electronic codebook mode encryption"
|
|
depends on HAS_HW_NRF_ECB
|
|
# Bluetooth controller uses the ECB peripheral directly
|
|
# (see subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/ecb.c),
|
|
# hence this driver cannot be enabled together with it.
|
|
depends on !BT_CTLR
|
|
help
|
|
Enable nRF HAL-based AES ECB encryption driver
|