Linux Kernel
3.7.1
|
Go to the source code of this file.
Data Structures | |
struct | nfc_ops |
struct | nfc_target |
struct | nfc_genl_data |
struct | nfc_dev |
Macros | |
#define | nfc_dev_info(dev, fmt, arg...) dev_info((dev), "NFC: " fmt "\n", ## arg) |
#define | nfc_dev_err(dev, fmt, arg...) dev_err((dev), "NFC: " fmt "\n", ## arg) |
#define | nfc_dev_dbg(dev, fmt, arg...) dev_dbg((dev), fmt "\n", ## arg) |
#define | NFC_TARGET_IDX_ANY -1 |
#define | NFC_MAX_GT_LEN 48 |
#define | NFC_ATR_RES_GT_OFFSET 15 |
#define | to_nfc_dev(_dev) container_of(_dev, struct nfc_dev, dev) |
Typedefs | |
typedef void(* | data_exchange_cb_t )(void *context, struct sk_buff *skb, int err) |
Variables | |
struct class | nfc_class |
#define to_nfc_dev | ( | _dev | ) | container_of(_dev, struct nfc_dev, dev) |
data_exchange_cb_t - Definition of nfc_data_exchange callback
: nfc_data_exchange cb_context parameter : response data : If an error has occurred during data exchange, it is the error number. Zero means no error.
When a rx or tx package is lost or corrupted or the target gets out of the operating field, err is -EIO.
nfc_target_lost - inform that an activated target went out of field
: The nfc device that had the activated target in field : the nfc index of the target
The device driver must call this function when the activated target goes out of the field. IMPORTANT: this function must not be called from an atomic context. In addition, it must also not be called from a context that would prevent the NFC Core to call other nfc ops entry point concurrently.
nfc_targets_found - inform that targets were found
: The nfc device that found the targets : array of nfc targets found : targets array size
The device driver must call this function when one or many nfc targets are found. After calling this function, the device driver must stop polling for targets. NOTE: This function can be called with targets=NULL and n_targets=0 to notify a driver error, meaning that the polling operation cannot complete. IMPORTANT: this function must not be called from an atomic context. In addition, it must also not be called from a context that would prevent the NFC Core to call other nfc ops entry point concurrently.