OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/bluetooth/controller/hci/hci_internal.h

47 lines
1.4 KiB
C
Raw Normal View History

Bluetooth: Controller: Add initial HCI implementation For the Link Layer to be able to communicate with the rest of the BLE stack in Zephyr, this barebones HCI controller implementation includes an initial version of the fundamental commands and events required. Jira: ZEP-702 Origin: Original Change-Id: I38bc9dae34e7075ab8b8178fd6b6659e2dec53b0 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 18:22:59 +08:00
/*
* Copyright (c) 2016 Nordic Semiconductor ASA
* Copyright (c) 2016 Vinayak Kariappa Chettimada
*
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 09:01:01 +08:00
* SPDX-License-Identifier: Apache-2.0
Bluetooth: Controller: Add initial HCI implementation For the Link Layer to be able to communicate with the rest of the BLE stack in Zephyr, this barebones HCI controller implementation includes an initial version of the fundamental commands and events required. Jira: ZEP-702 Origin: Original Change-Id: I38bc9dae34e7075ab8b8178fd6b6659e2dec53b0 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 18:22:59 +08:00
*/
Bluetooth: Controller: Refactor HCI files As part of the effort to consolidate the BLE Controller's HCI layer, the following files have been renamed: * hci.h -> hci_internal.h: contains the HCI API to be used by the driver * main.c -> hci_driver.c: Implement bt_driver and includes initialization and glue code Jira: ZEP-726 Change-Id: Ica8b3e114da42a766a1b14ce59558cacd899a1a7 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-09-15 16:07:56 +08:00
#ifndef _HCI_CONTROLLER_H_
#define _HCI_CONTROLLER_H_
Bluetooth: Controller: Add initial HCI implementation For the Link Layer to be able to communicate with the rest of the BLE stack in Zephyr, this barebones HCI controller implementation includes an initial version of the fundamental commands and events required. Jira: ZEP-702 Origin: Original Change-Id: I38bc9dae34e7075ab8b8178fd6b6659e2dec53b0 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 18:22:59 +08:00
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
#if defined(CONFIG_BT_HCI_ACL_FLOW_CONTROL)
Bluetooth: controller: Controller to Host flow control The Bluetooth Specification allows for optional Controller to Host flow control based on the same credit-based mechanism as the Host to Controller one. This is particularly useful in 2-chip solutions where the Host and the Controller are connected via a physical link (UART, SPI or similar) where the Host is sometimes required to ask the Controller to throttle its data traffic while still making sure that relevant events get through the line. This implementation is based on a simple queue of pending events and data that is populated whenever the Controller detects that the Host is out of buffers and then emptied whenever the Host notifies the Controller that is ready to receive data again. Events relevant to the connections are also queued to preserve the order of arrival. At this point the Controller ignores the connection handle sent by the Host and treats all connections equally, and it also queues events even for connections that have no data pending in the queue. Both this items can be improved if necessity arises. Note that Number of Completed Packets will still flow freely from the Controller to the Host regardless of the pending ACL data packets, which might lead to inconsistencies in the sequential order of certain operations that include bi-directional data transfer. Jira: ZEP-1735 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-04-07 15:53:02 +08:00
extern s32_t hci_hbuf_total;
extern u32_t hci_hbuf_sent;
extern u32_t hci_hbuf_acked;
extern atomic_t hci_state_mask;
#define HCI_STATE_BIT_RESET 0
#endif
#define HCI_CLASS_EVT_REQUIRED 0
#define HCI_CLASS_EVT_DISCARDABLE 1
#define HCI_CLASS_EVT_CONNECTION 2
#define HCI_CLASS_ACL_DATA 3
Bluetooth: controller: Fix Read Version Info VS cmd Use the macros generated during the build and located in version.h to fill in the version information in the Read Version Information VS command. Additionally reply with the correct hardware identifiers when running on Nordic hardware. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-09-01 22:20:46 +08:00
#if defined(CONFIG_SOC_FAMILY_NRF5)
#define BT_HCI_VS_HW_PLAT BT_HCI_VS_HW_PLAT_NORDIC
#if defined(CONFIG_SOC_SERIES_NRF51X)
#define BT_HCI_VS_HW_VAR BT_HCI_VS_HW_VAR_NORDIC_NRF51X;
#elif defined(CONFIG_SOC_SERIES_NRF52X)
#define BT_HCI_VS_HW_VAR BT_HCI_VS_HW_VAR_NORDIC_NRF52X;
#endif
#else
#define BT_HCI_VS_HW_PLAT 0
#define BT_HCI_VS_HW_VAR 0
#endif /* CONFIG_SOC_FAMILY_NRF5 */
Bluetooth: controller: Controller to Host flow control The Bluetooth Specification allows for optional Controller to Host flow control based on the same credit-based mechanism as the Host to Controller one. This is particularly useful in 2-chip solutions where the Host and the Controller are connected via a physical link (UART, SPI or similar) where the Host is sometimes required to ask the Controller to throttle its data traffic while still making sure that relevant events get through the line. This implementation is based on a simple queue of pending events and data that is populated whenever the Controller detects that the Host is out of buffers and then emptied whenever the Host notifies the Controller that is ready to receive data again. Events relevant to the connections are also queued to preserve the order of arrival. At this point the Controller ignores the connection handle sent by the Host and treats all connections equally, and it also queues events even for connections that have no data pending in the queue. Both this items can be improved if necessity arises. Note that Number of Completed Packets will still flow freely from the Controller to the Host regardless of the pending ACL data packets, which might lead to inconsistencies in the sequential order of certain operations that include bi-directional data transfer. Jira: ZEP-1735 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-04-07 15:53:02 +08:00
void hci_init(struct k_poll_signal *signal_host_buf);
Bluetooth: Controller: Redesign response buffer allocation for commands With an upcoming patch the HCI command buffers will be reused for the Command Complete/Status HCI events. The controller HCI code needs some refactoring to postpone the event buffer allocation so that the parsing state of the HCI command buffer isn't touched. Change-Id: I1f614fb9f02ed1886ca84198fbc8c64abc29e44f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-02-01 23:32:29 +08:00
struct net_buf *hci_cmd_handle(struct net_buf *cmd);
Bluetooth: Controller: Use net_buf for evt and ACL RX Use the net_buf structure directly when populating incoming ACL data or asynchronous events. This ensures that no additional memcpy() operations are required and removes completely the statically allocated buffers in hci.c. Jira: ZEP-726 Change-Id: I6ac8bd0becb7037ce8ecfac109f44832d23fcfd2 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-09-22 22:46:21 +08:00
void hci_evt_encode(struct radio_pdu_node_rx *node_rx, struct net_buf *buf);
Bluetooth: controller: Controller to Host flow control The Bluetooth Specification allows for optional Controller to Host flow control based on the same credit-based mechanism as the Host to Controller one. This is particularly useful in 2-chip solutions where the Host and the Controller are connected via a physical link (UART, SPI or similar) where the Host is sometimes required to ask the Controller to throttle its data traffic while still making sure that relevant events get through the line. This implementation is based on a simple queue of pending events and data that is populated whenever the Controller detects that the Host is out of buffers and then emptied whenever the Host notifies the Controller that is ready to receive data again. Events relevant to the connections are also queued to preserve the order of arrival. At this point the Controller ignores the connection handle sent by the Host and treats all connections equally, and it also queues events even for connections that have no data pending in the queue. Both this items can be improved if necessity arises. Note that Number of Completed Packets will still flow freely from the Controller to the Host regardless of the pending ACL data packets, which might lead to inconsistencies in the sequential order of certain operations that include bi-directional data transfer. Jira: ZEP-1735 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-04-07 15:53:02 +08:00
s8_t hci_get_class(struct radio_pdu_node_rx *node_rx);
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
#if defined(CONFIG_BT_CONN)
Bluetooth: controller: Issue Data Buffer Overflow event Whenever the HCI ACL flow control is violated by the Host, a Data Buffer Overflow event is now issued by the Controller (if enabled) to notify the Host of the buffer overrun. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-09-12 23:14:30 +08:00
int hci_acl_handle(struct net_buf *acl, struct net_buf **evt);
Bluetooth: Controller: Use net_buf for evt and ACL RX Use the net_buf structure directly when populating incoming ACL data or asynchronous events. This ensures that no additional memcpy() operations are required and removes completely the statically allocated buffers in hci.c. Jira: ZEP-726 Change-Id: I6ac8bd0becb7037ce8ecfac109f44832d23fcfd2 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-09-22 22:46:21 +08:00
void hci_acl_encode(struct radio_pdu_node_rx *node_rx, struct net_buf *buf);
Bluetooth: convert to using newly introduced integer sized types Convert code to use u{8,16,32,64}_t and s{8,16,32,64}_t instead of C99 integer types. Jira: ZEP-2051 Change-Id: I8f57a17f78e674aca5400f005db8975c9f9e150e Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-21 01:00:29 +08:00
void hci_num_cmplt_encode(struct net_buf *buf, u16_t handle, u8_t num);
Bluetooth: controller: Controller to Host flow control The Bluetooth Specification allows for optional Controller to Host flow control based on the same credit-based mechanism as the Host to Controller one. This is particularly useful in 2-chip solutions where the Host and the Controller are connected via a physical link (UART, SPI or similar) where the Host is sometimes required to ask the Controller to throttle its data traffic while still making sure that relevant events get through the line. This implementation is based on a simple queue of pending events and data that is populated whenever the Controller detects that the Host is out of buffers and then emptied whenever the Host notifies the Controller that is ready to receive data again. Events relevant to the connections are also queued to preserve the order of arrival. At this point the Controller ignores the connection handle sent by the Host and treats all connections equally, and it also queues events even for connections that have no data pending in the queue. Both this items can be improved if necessity arises. Note that Number of Completed Packets will still flow freely from the Controller to the Host regardless of the pending ACL data packets, which might lead to inconsistencies in the sequential order of certain operations that include bi-directional data transfer. Jira: ZEP-1735 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-04-07 15:53:02 +08:00
#endif
Bluetooth: Controller: Refactor HCI files As part of the effort to consolidate the BLE Controller's HCI layer, the following files have been renamed: * hci.h -> hci_internal.h: contains the HCI API to be used by the driver * main.c -> hci_driver.c: Implement bt_driver and includes initialization and glue code Jira: ZEP-726 Change-Id: Ica8b3e114da42a766a1b14ce59558cacd899a1a7 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-09-15 16:07:56 +08:00
#endif /* _HCI_CONTROLLER_H_ */