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_20.conf

29 lines
821 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_UART_CONSOLE=n
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
Bluetooth: init: Add CONFIG_BLUETOOTH_RFCOMM to prj_20.conf This makes sure RFCOMM support is build tested on each patch. Change-Id: I9cd60da1b0ab0db2b41487393fb59fe1b415ea01 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-19 20:49:28 +08:00
CONFIG_BLUETOOTH_RFCOMM=y
Bluetooth: init: Add CONFIG_BLUETOOTH_AVDTP to prj_20.conf This makes sure AVDTP support is build tested on each patch. Change-Id: Ia7cf94ca84fa01bd676a99b0df58ac745bbfc8c7 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-19 23:15:11 +08:00
CONFIG_BLUETOOTH_AVDTP=y
Bluetooth: Enable CONFIG_BLUETOOTH_DEBUG_AVDTP with prj_20.conf This ensures ADVTP patches are build tested with debug enabled. Change-Id: I5c09afea4a9df84b054d2383f0b53ff85fa5dcd5 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-28 16:26:31 +08:00
CONFIG_BLUETOOTH_DEBUG_AVDTP=y
Bluetooth: init: Add CONFIG_BLUETOOTH_A2DP to prj_20.conf This makes sure A2DP support is build tested on each patch. Change-Id: I9dba5c20d44d8ac92910e80c1ad97ac8d2207652 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-20 21:57:24 +08:00
CONFIG_BLUETOOTH_A2DP=y
Bluetooth: init: Add HFP to automated tests Adds HFP HF stack code to automated tests during build coverage. Change-Id: Ic7bf5f0077b38bbe0feed167935dee73c989a523 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2016-09-26 17:59:14 +08:00
CONFIG_BLUETOOTH_HFP_HF=y
CONFIG_BLUETOOTH_DEBUG_HFP_HF=y