7e7f05546d
So far, nRF 802.15.4 radio driver build was dependent on the 802.15.4 subsystem in Zephyr. While this was a reasonable approach for samples, it prevented the radio driver from being built as a standalone entity, which could be useful in some applications (e. g. running core nRF 802.15.4 radio driver tests with Zephyr). Resolve this, by providing a separate set of Kconfigs for the radio driver, therefore allowing to build it as a separate entity. The 802154 subsystem simply enables the radio driver module in this case. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
35 lines
994 B
Plaintext
35 lines
994 B
Plaintext
# Nordic Semiconductor nRF5 802.15.4 configuration options
|
|
|
|
# Copyright (c) 2017 Nordic Semiconductor ASA
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
menuconfig IEEE802154_NRF5
|
|
bool "nRF52 series IEEE 802.15.4 Driver"
|
|
depends on NETWORKING && HAS_HW_NRF_RADIO_IEEE802154
|
|
select NRF_802154_RADIO_DRIVER
|
|
|
|
if IEEE802154_NRF5
|
|
|
|
config IEEE802154_NRF5_DRV_NAME
|
|
string "nRF52 IEEE 802.15.4 Driver's name"
|
|
default "IEEE802154_nrf5"
|
|
help
|
|
This option sets the driver name
|
|
|
|
config IEEE802154_NRF5_RX_STACK_SIZE
|
|
int "Driver's internal RX thread stack size"
|
|
default 800
|
|
help
|
|
This option sets the driver's stack size for its internal RX thread.
|
|
The default value should be sufficient, but in case it proves to be
|
|
a too little one, this option makes it easy to play with the size.
|
|
|
|
config IEEE802154_NRF5_INIT_PRIO
|
|
int "nRF52 IEEE 802.15.4 initialization priority"
|
|
default 80
|
|
help
|
|
Set the initialization priority number. Do not mess with it unless
|
|
you know what you are doing.
|
|
|
|
endif
|