Lines Matching full:will

25 HCI events can also be received from the host controller. They will be handled
26 and a translation will be forwarded to NFC Core as needed. There are hooks to
38 support proprietary gates. This is the reason why the driver will pass a list
39 of proprietary gates that must be part of the session. HCI will ensure all
108   are required to send data to the tag. Some tag types will require custom
114 - check_presence() is an optional entry point that will be called regularly
116   not implemented, the core will not be able to push tag_lost events to the user
122 using nfc_hci_recv_frame(). HCI will take care of re-aggregation and handling
233 will be the syscall context. skb will return the result that was received in
238 The wait is not interruptible because it is guaranteed that the command will
241 MSGTXWQ context will then be scheduled and invoke nfc_hci_msg_tx_work().
242 This function will dequeue the next pending command and send its HCP fragments
243 to the lower layer which happens to be shdlc. It will then start a timer to be
255 The completion callback will then wake the syscall context.
264 the callback will be called with the result from the SMW context.
270 queued to HCI rx_queue and will be dispatched from HCI rx worker
277 Typically, such an event will be propagated to NFC Core from MSGRXWQ context.
287 went wrong below and know that expected events will probably never happen.
291   that any subsequent call to the driver will result in this error. Then it
293   problem above. shdlc stores a EREMOTEIO sticky status, which will trigger
297   frames. This thread will also check the shdlc sticky status and report to HCI
303   error from a lower layer, HCI will either complete the currently executing
308   active, it will send a tag discovered event with an empty tag list to the user
309   space to let it know that the poll operation will never be able to detect a
310   tag. If polling is not active and the error was sticky, lower levels will