Bluetooth: Kconfig Remove HOST_BUFFERS option

This option has not been used so far and will only contribute
unnecessary complexity in subsequent patches that introduce a concept
of combined RX buffers.

Change-Id: I53e0ce5155eebc352b84ba41b30ecb9d9958699f
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
Johan Hedberg 2016-12-21 17:39:55 +02:00
commit 6f429a38d8
4 changed files with 4 additions and 27 deletions

View file

@ -33,7 +33,6 @@ config BLUETOOTH_H4
bool "H:4 UART"
select UART_INTERRUPT_DRIVEN
select BLUETOOTH_UART
select BLUETOOTH_HOST_BUFFERS
depends on SERIAL
help
Bluetooth H:4 UART driver. Requires hardware flow control
@ -43,7 +42,6 @@ config BLUETOOTH_H5
bool "H:5 UART [EXPERIMENTAL]"
select UART_INTERRUPT_DRIVEN
select BLUETOOTH_UART
select BLUETOOTH_HOST_BUFFERS
depends on SERIAL
help
Bluetooth three-wire (H:5) UART driver. Implementation of HCI
@ -59,17 +57,6 @@ endchoice
endif # !BLUETOOTH_CONTROLLER
config BLUETOOTH_HOST_BUFFERS
bool "Host managed incoming data buffers"
help
Enable this to have the host stack manage incoming ACL data
and HCI event buffers. This makes sense for all HCI drivers
that talk to a controller running on a different CPU.
If the controller resides in the same address space it may
make sense to have the lower layers manage these buffers, in
which case this option can be left disabled.
config BLUETOOTH_DEBUG_HCI_DRIVER
bool "Bluetooth HCI driver debug"
depends on BLUETOOTH_DEBUG