Searched full:hci (Results 1 – 15 of 15) sorted by relevance
2 HCI backend for NFC Core11 The HCI layer implements much of the ETSI TS 102 622 V10.2.0 specification. It12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core14 to HCI commands and events.16 HCI chapter19 HCI registers as an nfc device with NFC Core. Requests coming from userspace are20 routed through netlink sockets to NFC Core and then to HCI. From this point,21 they are translated in a sequence of HCI commands sent to the HCI layer in the24 from HCI Rx context).25 HCI events can also be received from the host controller. They will be handled[all …]
18 In the normal (HCI) mode and in the firmware update mode read and22 In the normal (HCI) mode the protocol used is derived from the ETSI23 HCI specification. The firmware is updated using a specific protocol,24 which is different from HCI.26 HCI messages consist of an eight bit header and the message body. The27 header contains the message length. Maximum size for an HCI message is28 33. In HCI mode sent messages are tested for a correct33 For the ETSI HCI specification see
10 nfc-hci
4 $id: http://devicetree.org/schemas/i3c/mipi-i3c-hci.yaml#7 title: MIPI I3C HCI18 The MIPI I3C HCI (Host Controller Interface) specification defines27 https://www.mipi.org/specifications/i3c-hci31 const: mipi-i3c-hci47 compatible = "mipi-i3c-hci";
26 - description: HCI register33 - const: hci120 reg-names = "hci", "vs_hci", "unipro", "ufsp";
2 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor13 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
22 locally and also sent across to the WL128x via a HCI-VS
19 hci-muxed:22 Specifies that the chip is muxing NCI over HCI frames167 hci-muxed;
1 What: /sys/class/bluetooth/hci<index>/reset
95 Issuing a raw hci command98 Use hcitool to issue raw hci command, refer to hcitool manual
275 137 = /dev/vhci Bluetooth virtual HCI driver
22 standard BT HCI protocol with additional channels for the other functions.
56 a couple HCI (Hardware Configuration Interface) calls (0x6D and 0xA6) are
132 - pattern: "^hci[0-9]+-power$"
160 'H' C0-F0 net/bluetooth/hci.h conflict!