Kconfig: Move BT_WAIT_NOP into subsys/bluetooth/host
The CONFIG_BT_WAIT_NOP define is used only by zephyr/subsys/bluetooth/host/hci_core.c. It is also the only config in drivers/bluetooth that is in use when BT_CONTROLLER is enabled. Moving it into the bluetooth subsystem allows us to restructure the drivers/kconfig code such that the entire Bluetooth driver menu option is omitted when the BT_CONTROLLER is enabled. Moving it will also mean that all configs in drivers/bluetooth will now be related to configuring the source code in drivers/bluetooth. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
This commit is contained in:
parent
0848843c04
commit
2120beebf4
2 changed files with 9 additions and 9 deletions
|
@ -29,15 +29,6 @@ config BT_NRF51_PM
|
|||
Power Management support for Nordic BLE nRF51 chip. Allows to enable,
|
||||
disable the chip and handle wakeups.
|
||||
|
||||
config BT_WAIT_NOP
|
||||
bool "Wait for \"NOP\" Command Complete event during init"
|
||||
depends on BT_HCI
|
||||
help
|
||||
Some controllers emit a Command Complete event for the NOP
|
||||
opcode to indicate that they're ready to receive commands.
|
||||
This option should be selected if the controller used
|
||||
exhibits such behavior.
|
||||
|
||||
endmenu
|
||||
|
||||
endif # BT
|
||||
|
|
|
@ -62,6 +62,15 @@ config BT_HCI_TX_PRIO
|
|||
int
|
||||
default 7
|
||||
|
||||
config BT_WAIT_NOP
|
||||
bool "Wait for \"NOP\" Command Complete event during init"
|
||||
depends on BT_HCI
|
||||
help
|
||||
Some controllers emit a Command Complete event for the NOP
|
||||
opcode to indicate that they're ready to receive commands.
|
||||
This option should be selected if the controller used
|
||||
exhibits such behavior.
|
||||
|
||||
# Headroom that the driver needs for sending and receiving buffers.
|
||||
# Add a new 'default' entry for each new driver.
|
||||
config BT_HCI_RESERVE
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue