OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/net/bluetooth/Makefile

22 lines
344 B
Makefile
Raw Normal View History

drivers: bluetooth: nble: restructures Bluetooth Kconfig options This moves both the Bluetooth HCI and NBLE drivers under "Bluetooth Drivers" category. This also adds a selection for choosing Bluetooth stacks as the bulk of both HCI and NBLE stacks cannot be compiled together. Note that this does not move the source files. That should be done in a separate change. Change-Id: I32fa7097ada0fdc52bcc745adb78c7273f4023c6 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-17 04:05:56 +08:00
obj-$(CONFIG_BLUETOOTH_STACK_HCI) = \
hci_core.o \
Bluetooth: Always compile in UUID support This is also useful for Broadcaster and Observer roles and shouldn't depend on connection support. Change-Id: I85003253455c3949344e26d24a5fb3a718115947 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-10-29 16:54:43 +08:00
uuid.o
Bluetooth: Add initial Kconfig split options This allows to specify which roles are supported. Broadcaster and Observer roles are always supported. Image size reduction for samples apps: beacon 43148 -> 15196 central 46892 -> 46356 peripheral 47532 -> 45940 Change-Id: If260c13d63651b9b54df5bafc2c412b01dcb1eb0 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-08 00:25:59 +08:00
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 22:54:07 +08:00
obj-$(CONFIG_BLUETOOTH_DEBUG_MONITOR) += monitor.o
Bluetooth: Add option for disabling SMP support This allows to not compile SMP support for devices that don't require pairing. It is required to support SMP channel and reply with error for any command received even if pairing is not supported. To handle this cleanly a null smp implementation is used that case. Change-Id: I656a52dac882839db904eee65f25a4e29ea2d8c2 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-09 23:27:16 +08:00
ifeq ($(CONFIG_BLUETOOTH_CONN),y)
obj-y += conn.o \
l2cap.o \
att.o \
Bluetooth: Always compile in UUID support This is also useful for Broadcaster and Observer roles and shouldn't depend on connection support. Change-Id: I85003253455c3949344e26d24a5fb3a718115947 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-10-29 16:54:43 +08:00
gatt.o
Bluetooth: Add option for disabling SMP support This allows to not compile SMP support for devices that don't require pairing. It is required to support SMP channel and reply with error for any command received even if pairing is not supported. To handle this cleanly a null smp implementation is used that case. Change-Id: I656a52dac882839db904eee65f25a4e29ea2d8c2 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-09 23:27:16 +08:00
ifeq ($(CONFIG_BLUETOOTH_SMP),y)
obj-y += smp.o \
keys.o
else
obj-y += smp_null.o
endif
Bluetooth: Build keys support if BR/EDR is enabled BR/EDR requires keys support. Change-Id: I890b4e56e4e4808cab5579ed280529e11de2cb66 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-03-23 16:47:47 +08:00
obj-$(CONFIG_BLUETOOTH_BREDR) += keys.o
Bluetooth: Add option for disabling SMP support This allows to not compile SMP support for devices that don't require pairing. It is required to support SMP channel and reply with error for any command received even if pairing is not supported. To handle this cleanly a null smp implementation is used that case. Change-Id: I656a52dac882839db904eee65f25a4e29ea2d8c2 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-09 23:27:16 +08:00
endif