patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/drivers/bluetooth/Kconfig

44 lines
920 B
Plaintext
Raw Normal View History

Kbuild: Kconfig license headers. This commit add license headers to Kconfig files. Change-Id: I79e60263b8c7b696463ecc84b8ad411af5415117 Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com>
2015-05-20 18:40:39 +02:00
# Kconfig - Bluetooth LE driver configuration options
Kbuild: Bluetooth driver support. This commit adds the Makefile and Kconfig files to support the bluetooth driver in the Kbuild system. Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com> Change-Id: I1f72b13aca8fb098eece04c4f0e1b680639b520f
2015-05-11 04:52:56 +02:00
#
Bluetooth: Update Intel copyright for files modified in 2016 Change-Id: I10a7cab9a7f911b9f64e17bf24ddce82c2f08c40 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-06-10 11:10:18 +02:00
# Copyright (c) 2015-2016 Intel Corporation
Kbuild: Bluetooth driver support. This commit adds the Makefile and Kconfig files to support the bluetooth driver in the Kbuild system. Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com> Change-Id: I1f72b13aca8fb098eece04c4f0e1b680639b520f
2015-05-11 04:52:56 +02:00
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 02:01:01 +01:00
# SPDX-License-Identifier: Apache-2.0
Kbuild: Bluetooth driver support. This commit adds the Makefile and Kconfig files to support the bluetooth driver in the Kbuild system. Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com> Change-Id: I1f72b13aca8fb098eece04c4f0e1b680639b520f
2015-05-11 04:52:56 +02:00
#
#
# Bluetooth options
#
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-16 21:05:56 +01:00
if BLUETOOTH
menu "Bluetooth Drivers"
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 11:23:21 +01:00
if BLUETOOTH_HCI
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 15:55:01 +02:00
source "drivers/bluetooth/hci/Kconfig"
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 11:23:21 +01:00
endif
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-16 21:05:56 +01:00
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 11:23:21 +01:00
if BLUETOOTH_CUSTOM
Bluetooth: Remove support for NBLE NBLE has been deprecated for a few releases now and can be removed. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-25 03:09:15 +02:00
# Insert here any custom (non-HCI) offload drives
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 11:23:21 +01:00
endif
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-16 21:05:56 +01:00
Bluetooth: Add option for PM with Nordic BLE chip The config option handles enabling, disabling and power management operations with Nordic nRF51 BLE chip. Change-Id: I816062a7fb17c9e57c234113a2cecdebceb407b6 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2016-04-05 08:42:30 +02:00
config BLUETOOTH_NRF51_PM
Bluetooth: Fix BLUETOOTH_NRF51_PM Kconfig definition Clarify the name of the option and add a dependency to Arduino 101 which is the only known board that is currently known to need it. Change-Id: Ibfb96cba202f34464b45b922da599da70c038d12 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-07 09:50:52 +02:00
bool "nRF51 Power Management [EXPERIMENTAL]"
Bluetooth: Remove support for NBLE NBLE has been deprecated for a few releases now and can be removed. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-25 03:09:15 +02:00
depends on BLUETOOTH_H4
Bluetooth: Add option for PM with Nordic BLE chip The config option handles enabling, disabling and power management operations with Nordic nRF51 BLE chip. Change-Id: I816062a7fb17c9e57c234113a2cecdebceb407b6 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2016-04-05 08:42:30 +02:00
help
Power Management support for Nordic BLE nRF51 chip. Allows to enable,
disable the chip and handle wakeups.
Bluetooth: Add support for waiting for "NOP" Command Complete Some controllers will emit an initial "NOP" Command Complete event during initialization and expect the host to only send commands once this event has been received. This patch adds a new Kconfig option to be used in the case of such controllers and defaults this to true on Arduino 101 with the H:4 driver where this behavior is currently observed. Change-Id: I440f14a7c07ac27545febf9f85ebcc343e2a4558 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-18 10:45:45 +02:00
config BLUETOOTH_WAIT_NOP
bool "Wait for \"NOP\" Command Complete event during init"
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 11:23:21 +01:00
depends on BLUETOOTH_HCI
Bluetooth: Add support for waiting for "NOP" Command Complete Some controllers will emit an initial "NOP" Command Complete event during initialization and expect the host to only send commands once this event has been received. This patch adds a new Kconfig option to be used in the case of such controllers and defaults this to true on Arduino 101 with the H:4 driver where this behavior is currently observed. Change-Id: I440f14a7c07ac27545febf9f85ebcc343e2a4558 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-18 10:45:45 +02:00
help
Some controllers emit a Command Complete event for the NOP
opcode to indicate that they're ready to receive commands.
This option should be selected if the controller used
exhibits such behavior.
Kbuild: Bluetooth driver support. This commit adds the Makefile and Kconfig files to support the bluetooth driver in the Kbuild system. Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com> Change-Id: I1f72b13aca8fb098eece04c4f0e1b680639b520f
2015-05-11 04:52:56 +02:00
endmenu
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-16 21:05:56 +01:00
endif # BLUETOOTH
Reference in a new issue Copy permalink