zephyr/drivers/bluetooth/Makefile

ccflags-y += -I$(srctree)/subsys/bluetooth

obj-y += hci/
obj-$(CONFIG_BT_NRF51_PM) += nrf51_pm.o
Bluetooth: Move common code to common/ Since more and more code is going to be reused by both the Host and the Controller, this commit introduces a common/ folder that will contain everything that is not tied to one of the two components but shared by them. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2017-05-10 22:27:16 +08:00			`ccflags-y += -I$(srctree)/subsys/bluetooth`

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			`obj-y += hci/`
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2017-08-09 14:21:11 +08:00			`obj-$(CONFIG_BT_NRF51_PM) += nrf51_pm.o`