OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/bluetooth/init/prj_21.conf

22 lines
635 B
Plaintext
Raw Normal View History

Bluetooth: tests: Add automated tests for new monitor code Add two new test cases to exercise the code in monitor.c. Change-Id: I66ae70e0d3b61d3b852916333019e1ed2c5c6cf4 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-22 18:47:20 +08:00
CONFIG_BLUETOOTH=y
CONFIG_BLUETOOTH_PERIPHERAL=y
CONFIG_BLUETOOTH_CENTRAL=y
CONFIG_BLUETOOTH_SMP=y
CONFIG_BLUETOOTH_SIGNING=y
CONFIG_BLUETOOTH_SMP_SC_ONLY=y
CONFIG_BLUETOOTH_TINYCRYPT_ECC=y
CONFIG_BLUETOOTH_USE_DEBUG_KEYS=y
CONFIG_BLUETOOTH_L2CAP_DYNAMIC_CHANNEL=y
CONFIG_BLUETOOTH_GATT_CLIENT=y
CONFIG_BLUETOOTH_DEBUG_MONITOR=y
CONFIG_BLUETOOTH_DEBUG_HCI_CORE=y
CONFIG_BLUETOOTH_DEBUG_CONN=y
CONFIG_BLUETOOTH_DEBUG_KEYS=y
CONFIG_BLUETOOTH_DEBUG_L2CAP=y
CONFIG_BLUETOOTH_DEBUG_SMP=y
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 21:55:01 +08:00
CONFIG_BLUETOOTH_DEBUG_HCI_DRIVER=y
Bluetooth: tests: Add automated tests for new monitor code Add two new test cases to exercise the code in monitor.c. Change-Id: I66ae70e0d3b61d3b852916333019e1ed2c5c6cf4 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-22 18:47:20 +08:00
CONFIG_BLUETOOTH_SMP_SELFTEST=y
CONFIG_BLUETOOTH_DEBUG_ATT=y
CONFIG_BLUETOOTH_DEBUG_GATT=y
CONFIG_BLUETOOTH_BREDR=y