Driver Operations Bluetooth HCI driver operations More...

#include <zephyr/drivers/bluetooth.h>

Data Fields
bt_hci_api_open_t	open
	REQ Open the HCI transport.
bt_hci_api_close_t	close
	OPT Close the HCI transport.
bt_hci_api_send_t	send
	REQ Send HCI buffer to controller.
bt_hci_api_setup_t	setup
	OPT HCI vendor-specific setup.

Detailed Description

Driver Operations Bluetooth HCI driver operations

This is the driver API structure any Bluetooth HCI driver needs to define. It contains function pointers to the operations the driver implements, as well as any other driver-specific constant data.

Members marked with REQ MUST be set by the driver, whereas those marked with OPT are optional.

See also: DEVICE_DT_INST_DEFINE(); DEVICE_DT_DEFINE(); DEVICE_API()

Field Documentation

◆ close

bt_hci_api_close_t bt_hci_driver_api::close

OPT Close the HCI transport.

◆ open

bt_hci_api_open_t bt_hci_driver_api::open

REQ Open the HCI transport.

◆ send

bt_hci_api_send_t bt_hci_driver_api::send

REQ Send HCI buffer to controller.

◆ setup

bt_hci_api_setup_t bt_hci_driver_api::setup

OPT HCI vendor-specific setup.

Attention: Available only when the following Kconfig option is enabled: CONFIG_BT_HCI_SETUP.

The documentation for this struct was generated from the following file:

zephyr/drivers/bluetooth.h