user/sven/linux.git/include/uapi/linux/nfc.h, branch v3.12.34

NFC: netlink: Add result of firmware operation to completion event

2013-08-13T23:12:58Z

Result is added as an NFC_ATTR_FIRMWARE_DOWNLOAD_STATUS attribute containing the standard errno positive value of the completion result. This event will be sent when the firmare download operation is done and will contain the operation result. Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz

NFC: Add a GET_SE netlink API

2013-08-13T22:35:19Z

In order to fetch the discovered secure elements from an NFC controller, we need to send a netlink command that will dump the list of available SEs from NFC. Signed-off-by: Samuel Ortiz

NFC: Define secure element connectivity and transaction events

2013-08-13T22:35:17Z

The SE_CONNECTIVITY event is for an SE to request connection to e.g. a modem. The SE_TRANSACTION one is sent when an application running on a specific SE wants to notify the host CPU about the end of a transaction. Those events respectively map to the EVT_CONNECTIVITY and the EVT_TRANSACTION HCI events. Signed-off-by: Samuel Ortiz

NFC: Document secure element addition/removal netlink events

2013-08-13T22:35:16Z

Signed-off-by: Samuel Ortiz

NFC: netlink: Rename CMD_FW_UPLOAD to CMD_FW_DOWNLOAD

2013-07-30T23:19:43Z

Loading a firmware into a target is typically called firmware download, not firmware upload. So we rename the netlink API to NFC_CMD_FW_DOWNLOAD in order to avoid any terminology confusion from userspace. Signed-off-by: Samuel Ortiz

NFC: Send netlink events for secure elements additions and removals

2013-06-14T11:44:59Z

When an NFC driver or host controller stack discovers a secure element, it will call nfc_add_se(). In order for userspace applications to use these secure elements, a netlink event will then be sent with the SE index and its type. With that information userspace applications can decide wether or not to enable SEs, through their indexes. Signed-off-by: Samuel Ortiz

NFC: Add secure elements addition and removal API

2013-06-14T11:44:58Z

This API will allow NFC drivers to add and remove the secure elements they know about or detect. Typically this should be called (asynchronously or not) from the driver or the host interface stack detect_se hook. Signed-off-by: Samuel Ortiz

NFC: pn533: Copy NFCID2 through ATR_REQ

2013-06-14T11:44:18Z

When using NFC-F we should copy the NFCID2 buffer that we got from SENSF_RES through the ATR_REQ NFCID3 buffer. Not doing so violates NFC Forum digital requirement #189. Signed-off-by: Samuel Ortiz

NFC: Add firmware upload netlink command

2013-06-13T22:26:08Z

As several NFC chipsets can have their firmwares upgraded and reflashed, this patchset adds a new netlink command to trigger that the driver loads or flashes a new firmware. This will allows userspace triggered firmware upgrade through netlink. The firmware name or hint is passed as a parameter, and the driver will eventually fetch the firmware binary through the request_firmware API. The cmd can only be executed when the nfc dev is not in use. Actual firmware loading/flashing is an asynchronous operation. Result of the operation shall send a new event up to user space through the nfc dev multicast socket. During operation, the nfc dev is not openable and thus not usable. Signed-off-by: Eric Lapuyade Signed-off-by: Samuel Ortiz

NFC: llcp: Add support in getsockopt for RW, LTO, and MIU remote parameters

2013-04-11T14:28:59Z

Useful for LLCP validation tests. Signed-off-by: Thierry Escande Signed-off-by: Samuel Ortiz