linux-toradex.git/net/nfc/core.c, branch v3.4.83 Linux kernel for Apalis and Colibri modules NFC: Core code identation fixes 2012-03-06T20:16:25+00:00 Samuel Ortiz sameo@linux.intel.com 2012-03-05T00:03:53+00:00 0a40acb24602783fcf6881f915659148aa9807d7 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Remove the rf mode parameter from the DEP link up routine 2012-03-06T20:16:23+00:00 Samuel Ortiz sameo@linux.intel.com 2012-03-05T00:03:50+00:00 47807d3dbb62e93850cbcb797db1a9ee1806f986 When calling nfc_dep_link_up, we implicitely are in initiator mode. Which means we also can provide the general bytes as a function argument, as all drivers will eventually request them. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
When calling nfc_dep_link_up, we implicitely are in initiator mode.
Which means we also can provide the general bytes as a function argument,
as all drivers will eventually request them.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: NFC core layer should not set the target_idx 2012-01-24T19:32:28+00:00 Ilan Elias ilane@ti.com 2012-01-18T11:16:13+00:00 25a1d9dc850b1bdcc4760eb625f0a67057f54d26 The NFC core layer should not set the target_idx. Instead, the driver layer (e.g. NCI, PN533) should set the target_idx, so that it will be able to identify the target when its I/F (e.g. activate_target) is called. This is required in order to support multiple targets. Note that currently supported drivers (PN533 and NCI) don't use the target_idx in their implementation. Signed-off-by: Ilan Elias <ilane@ti.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
The NFC core layer should not set the target_idx.
Instead, the driver layer (e.g. NCI, PN533) should set the
target_idx, so that it will be able to identify the target
when its I/F (e.g. activate_target) is called.
This is required in order to support multiple targets.
Note that currently supported drivers (PN533 and NCI) don't
use the target_idx in their implementation.

Signed-off-by: Ilan Elias <ilane@ti.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Initial LLCP support 2011-12-14T19:50:13+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:12+00:00 d646960f7986fefb460a2b062d5ccc8ccfeacc3a This patch is an initial implementation for the NFC Logical Link Control protocol. It's also known as NFC peer to peer mode. This is a basic implementation as it lacks SDP (services Discovery Protocol), frames aggregation support, and frame rejecion parsing. Follow up patches will implement those missing features. This code has been tested against a Nexus S phone implementing LLCP 1.0. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
This patch is an initial implementation for the NFC Logical Link Control
protocol. It's also known as NFC peer to peer mode.
This is a basic implementation as it lacks SDP (services Discovery
Protocol), frames aggregation support, and frame rejecion parsing.
Follow up patches will implement those missing features.
This code has been tested against a Nexus S phone implementing LLCP 1.0.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Set and get DEP general bytes 2011-12-14T19:50:13+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:10+00:00 541d920b05b538ec0d9ae8ce619ee4fc6fb19e32 Without an API for setting and getting the local and remote general bytes, drivers won't be able to properly establish a DEP link. This API also allows them to propagate the remote general bytes they get from the DEP link establishment up to the LLCP layer. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
Without an API for setting and getting the local and remote general bytes,
drivers won't be able to properly establish a DEP link.
This API also allows them to propagate the remote general bytes they get
from the DEP link establishment up to the LLCP layer.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Add a DEP link control netlink command 2011-12-14T19:50:12+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:09+00:00 1ed28f610653e9b18433c6d87e9d333b7e3e886e NFC-DEP (Data Exchange Protocol) is an NFC MAC layer. This command allows to enable and disable the DEP link on to which e.g. LLCP can run. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
NFC-DEP (Data Exchange Protocol) is an NFC MAC layer.
This command allows to enable and disable the DEP link on to which e.g.
LLCP can run.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Add tx skb allocation routine 2011-12-14T19:50:12+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:06+00:00 7c7cd3bfec68fee33b30d177df6a6a0c4bbdc59d This is a factorization of the current rawsock tx skb allocation routine, as it will be used by the LLCP code. We also rename nfc_alloc_skb to nfc_alloc_recv_skb for consistency sake. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
This is a factorization of the current rawsock tx skb allocation routine,
as it will be used by the LLCP code.
We also rename nfc_alloc_skb to nfc_alloc_recv_skb for consistency sake.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: Add function name to the NFC pr_fmt() routine 2011-12-14T19:50:12+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:05+00:00 52858b51b2c779a8f9db32accf774b165522ad81 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
nfc: Remove unused nfc_printk and nfc_<level> macros 2011-11-30T20:08:37+00:00 Joe Perches joe@perches.com 2011-11-29T19:37:34+00:00 538af1344ab21cd2b638e779c2e82550a886b26e All uses have been removed, so killing what's not necessary. Signed-off-by: Joe Perches <joe@perches.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
All uses have been removed, so killing what's not necessary.

Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
nfc: Convert nfc_dbg to pr_debug 2011-11-30T20:08:36+00:00 Joe Perches joe@perches.com 2011-11-29T19:37:33+00:00 20c239c1390bd6f3bb389fe1a7e8307f29f52563 Using the standard debugging mechanisms is better than subsystem specific ones when the subsystem doesn't use a specific struct. Coalesce long formats. Signed-off-by: Joe Perches <joe@perches.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 
Using the standard debugging mechanisms is better than
subsystem specific ones when the subsystem doesn't use
a specific struct.

Coalesce long formats.

Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>