linux.git/net/nfc/core.c, branch v3.12

NFC: Update secure element state

2013-08-13T23:13:40+00:00

The secure element state was not updated from the enable/disable ops,
leaving the SE state to disabled for ever.

Signed-off-by: Arron Wang 
Signed-off-by: Samuel Ortiz

NFC: Fix secure element state check

2013-08-13T23:13:38+00:00

Another typo from the initial commit where we check for the secure
element type field instead of its state when enabling or disabling it.

Signed-off-by: Arron Wang 
Signed-off-by: Samuel Ortiz

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

2013-08-13T23:12:58+00:00

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: Fix SE discovery failure warning condition

2013-08-13T22:35:19+00:00

This is a typo coming from the initial implementation. se_discover fails
when it returns something different than zero and we should only display
a warning in that case.

Signed-off-by: Samuel Ortiz

NFC: netlink: Rename CMD_FW_UPLOAD to CMD_FW_DOWNLOAD

2013-07-30T23:19:43+00:00

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: Add secure element enablement internal API

2013-06-14T11:45:01+00:00

Called via netlink, this API will enable or disable a specific secure
element. When a secure element is enabled, it will handle card emulation
and more generically ISO-DEP target mode, i.e. all target mode cases
except for p2p target mode.

Signed-off-by: Samuel Ortiz

NFC: Remove and free all SEs when releasing an NFC device

2013-06-14T11:45:00+00:00

Signed-off-by: Samuel Ortiz

NFC: Send netlink events for secure elements additions and removals

2013-06-14T11:44:59+00:00

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:58+00:00

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: Extend and fix the internal secure element API

2013-06-14T11:44:53+00:00

Secure elements need to be discovered after enabling the NFC controller.
This is typically done by the NCI core and the HCI drivers (HCI does not
specify how to discover SEs, it is left to the specific drivers).
Also, the SE enable/disable API explicitely takes a SE index as its
argument.

Signed-off-by: Samuel Ortiz