kernel/include/net/nfc/hci.h, branch linux-4.15.y

NFC: Introduce vendor commands structures

2015-06-08T23:20:19Z

Together with inline routines to associate a vendor commands array with an NFC device. Vendor commands allow vendors to implement their very specific operations from driver code instead of adding new stack ops for non NFC generic commands. Vendors need to select their own unique IDs and use that as a namespace for defining sub commands. Signed-off-by: Samuel Ortiz

nfc: hci: Add comment to explain NFC_HCI_MAX_PIPES

2015-04-05T22:18:20Z

According to specification etsi 102 622 chapter 4.4 pipes identifier is 7 bits long giving a 127 possible pipes value. Reported-by: Dan Carpenter Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add cmd_received handler

2015-01-27T23:03:34Z

When a command is received, it is sometime needed to let the CLF driver do some additional operations. (ex: count remaining pipe notification...) Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Change nfc_hci_send_response gate parameter to pipe

2015-01-27T22:55:20Z

As there can be several pipes connected to the same gate, we need to know which pipe ID to use when sending an HCI response. A gate ID is not enough. Instead of changing the nfc_hci_send_response() API to something not aligned with the rest of the HCI API, we call nfc_hci_hcp_message_tx directly. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add pipes table to reference them with a tuple {gate, host}

2015-01-27T22:39:32Z

In order to keep host source information on specific hci event (such as evt_connectivity or evt_transaction) and because 2 pipes can be connected to the same gate, it is necessary to add a table referencing every pipe with a {gate, host} tuple. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Change event_received handler gate parameter to pipe

2015-01-27T22:39:23Z

Several pipes may point to the same CLF gate, so getting the gate ID as an input is not enough. For example dual secure element may have 2 pipes (1 for uicc and 1 for eSE) pointing to the connectivity gate. As resolving gate and host IDs can be done from a pipe, we now pass the pipe ID to the event received handler. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add specific hci macro to not create a pipe

2014-12-02T21:48:13Z

Some pipe are only created by other host (different than the Terminal Host). The pipe values will for example be notified by NFC_HCI_ADM_NOTIFY_PIPE_CREATED. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add se_io HCI operand

2014-12-02T00:49:58Z

se_io allows to send apdu over the CLF to the embedded Secure Element. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add stop_poll HCI operand.

2014-07-22T23:04:31Z

stop_poll allows to stop CLF reader polling. Some other operations might be necessary for some CLF to stop polling. For example in card mode. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz

NFC: hci: Add load_session HCI operand

2014-04-21T22:37:26Z

load_session allows a CLF to restore the gate <-> pipe table from some proprietary location. The main advantage to add this function is to reduce the memory wear by running pipe creation (and storing) only once. Signed-off-by: Christophe Ricard Signed-off-by: Samuel Ortiz