Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v3.4.95 2012-03-06T20:16:25+00:00 2012-03-06T20:16:25+00:00 Samuel Ortiz sameo@linux.intel.com 2012-03-05T00:03:53+00:00 urn:sha1:0a40acb24602783fcf6881f915659148aa9807d7 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 2012-03-06T20:16:23+00:00 Samuel Ortiz sameo@linux.intel.com 2012-03-05T00:03:50+00:00 urn:sha1: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> 2012-01-24T19:32:28+00:00 Ilan Elias ilane@ti.com 2012-01-18T11:16:13+00:00 urn:sha1: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> 2012-01-24T19:21:15+00:00 Ilan Elias ilane@ti.com 2012-01-17T09:06:43+00:00 urn:sha1:d5a2ca60e41fec4ede7b82d3608278523cffe77b Export new attributes sensb_res for tech B and sensf_res for tech F in the target info (returned as a response to NFC_CMD_GET_TARGET). The max size of the attributes nfcid1, sensb_res and sensf_res is exported to user space though include/linux/nfc. Signed-off-by: Ilan Elias <ilane@ti.com> Acked-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 2012-01-04T19:30:43+00:00 Ilan Elias ilane@ti.com 2011-12-22T09:51:54+00:00 urn:sha1:288e0713f469c03dbc412153b5341d6dfc2c9907 The nfcid1 is the NFC-A identifier. It is exported as an attribute of the target info (returned as a response to NFC_CMD_GET_TARGET). Signed-off-by: Ilan Elias <ilane@ti.com> Acked-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> 2011-12-14T19:50:13+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:10+00:00 urn:sha1: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> 2011-12-14T19:50:12+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:09+00:00 urn:sha1: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> 2011-12-14T19:50:12+00:00 Samuel Ortiz sameo@linux.intel.com 2011-12-14T15:43:06+00:00 urn:sha1: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> 2011-09-20T18:43:49+00:00 Ilan Elias ilane@ti.com 2011-09-18T08:19:34+00:00 urn:sha1:55eb94f9e923cba376cdf48ea5ab28d81116bead The file nfc.h was moved from include/net to include/net/nfc, since new NFC header files will be added to include/net/nfc. Signed-off-by: Ilan Elias <ilane@ti.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>