Lines Matching refs:an

10 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
11 backend, implementing an abstract nfc device and translating NFC Core API
17 HCI registers as an nfc device with NFC Core. Requests coming from userspace are
34 The Session initialization is an HCI standard which must unfortunately
88 - hci_ready() is an optional entry point that is called right after the hci
92 - start_poll() is an optional entrypoint that shall set the hardware in polling
99 - target_from_gate() is an optional entrypoint to return the nfc protocols
101 - complete_target_discovered() is an optional entry point to let the driver
111 - check_presence() is an optional entry point that will be called regularly
112 by the core to check that an activated tag is still in the field. If this is
115 - event_received() is called to handle an event coming from the chip. Driver
136 layers such as an llc to store the frame for re-emission, this function must
178 An HCI based driver for an NXP PN544, connected through I2C bus, and using
203 Workflow executing an HCI command (using shdlc)
206 Executing an HCI command can easily be performed synchronously using the
228 receives incoming frames in an skb queue filled from the driver IRQ handler.
246 Workflow receiving an HCI event or command
253 NFC_HCI_EVT_TARGET_DISCOVERED event from PN544 requires to issue an
257 Typically, such an event will be propagated to NFC Core from MSGRXWQ context.
262 Errors that occur synchronously with the execution of an NFC Core request are
270 - driver (pn544) fails to deliver an incoming frame: it stores the error such
278 when it discovers it is not able to run anymore because of an unrecoverable
282 - HCI: if an internal HCI error happens (frame is lost), or HCI is reported an
286 - NFC Core: when NFC Core is notified of an error from below and polling is
287 active, it will send a tag discovered event with an empty tag list to the user