2020-03-27 14:52:36 +01:00
|
|
|
# nRF9160 DK NRF52840 board configuration
|
2019-11-01 13:45:29 +01:00
|
|
|
|
2019-01-24 18:22:58 +01:00
|
|
|
# Copyright (c) 2018 Nordic Semiconductor ASA
|
|
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
|
2020-03-27 14:52:36 +01:00
|
|
|
if BOARD_NRF9160DK_NRF52840
|
2019-01-24 18:22:58 +01:00
|
|
|
|
|
|
|
|
config BOARD
|
2020-03-27 14:52:36 +01:00
|
|
|
default "nrf9160dk_nrf52840"
|
2019-01-24 18:22:58 +01:00
|
|
|
|
|
|
|
|
config IEEE802154_NRF5
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 12:29:31 +01:00
|
|
|
default y
|
2020-02-10 04:18:50 +01:00
|
|
|
depends on IEEE802154
|
2019-01-24 18:22:58 +01:00
|
|
|
|
2019-02-07 18:24:30 +01:00
|
|
|
config BT_CTLR
|
|
|
|
|
default BT
|
|
|
|
|
|
2020-03-27 14:52:36 +01:00
|
|
|
endif # BOARD_NRF9160DK_NRF52840
|
