Lines Matching +full:send +full:- +full:not +full:- +full:empty

5 - Author: Eric Lapuyade, Samuel Ortiz
6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
9 -------
12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
17 ---
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
35 --------------------------
41 In case the chip supports pre-opened gates and pseudo-static pipes, the driver
45 -------------------
50 This is consistent with the driver need to send commands to proprietary gates
54 ----------------
61 --------------
90 - open() and close() shall turn the hardware on and off.
91 - hci_ready() is an optional entry point that is called right after the hci
94 - xmit() shall simply write a frame to the physical link.
95 - start_poll() is an optional entrypoint that shall set the hardware in polling
98 - dep_link_up() is called after a p2p target has been detected, to finish
101 - dep_link_down() is called to bring the p2p link down.
102 - target_from_gate() is an optional entrypoint to return the nfc protocols
104 - complete_target_discovered() is an optional entry point to let the driver
107 - im_transceive() must be implemented by the driver if proprietary HCI commands
108   are required to send data to the tag. Some tag types will require custom
113 - tm_send() is called to send data in the case of a p2p connection
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
118 - event_received() is called to handle an event coming from the chip. Driver
122 using nfc_hci_recv_frame(). HCI will take care of re-aggregation and handling
126 --------------
141 	Send a data frame to the chip. Note that to enable higher
142 	layers such as an llc to store the frame for re-emission, this
143 	function must not alter the skb. It must also not return a positive
149 ---
186 Again, note that the llc does not handle the physical link. It is thus very
190 ----------------
196 ------------------
199 - IRQ handler (IRQH):
203 - SHDLC State Machine worker (SMW)
209 - HCI Tx Cmd worker (MSGTXWQ)
215 - HCI Rx worker (MSGRXWQ)
219 - Syscall context from a userspace call (SYSCALL)
224 -----------------------------------------------
238 The wait is not interruptible because it is guaranteed that the command will
242 This function will dequeue the next pending command and send its HCP fragments
247 handles shdlc framing in and out. It uses the driver xmit to send frames and
267 ------------------------------------------
269 HCI commands or events are not dispatched from SMW context. Instead, they are
280 ----------------
290 - driver (pn544) fails to deliver an incoming frame: it stores the error such
296 - SMW is basically a background thread to handle incoming and outgoing shdlc
298   when it discovers it is not able to run anymore because of an unrecoverable
302 - HCI: if an internal HCI error happens (frame is lost), or HCI is reported an
307 - NFC Core: when NFC Core is notified of an error from below and polling is
308   active, it will send a tag discovered event with an empty tag list to the user
310   tag. If polling is not active and the error was sticky, lower levels will