kernel/git/stable/linux.git/include/net/nfc/shdlc.h, branch masterLinux kernel stable treehttps://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master2012-09-24T22:17:26+00:00NFC: Changed HCI and PN544 HCI driver to use the new HCI LLC Core2012-09-24T22:17:26+00:00Eric Lapuyadeeric.lapuyade@linux.intel.com2012-09-18T17:45:48+00:00urn:sha1:412fda538f4b1317ecd0fbe6e5bc9124792bea88
The previous shdlc HCI driver and its header are removed from the tree.
PN544 now registers directly with HCI and passes the name of the llc it
requires (shdlc).
HCI instantiation now allocates the required llc instance. The llc is
started when the HCI device is brought up.
Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: Modified hci_transceive to become an asynchronous operation2012-09-24T22:17:25+00:00Eric Lapuyadeeric.lapuyade@linux.intel.com2012-09-11T08:43:50+00:00urn:sha1:f3e8fb552789f4845e60b11c47b676d14b9488e5
This enables the completion callback to be called from a different
context, preventing a possible deadlock if the callback resulted in the
invocation of a nested call to the currently locked nfc_dev.
This is also more in line with the im_transceive nfc_ops for NFC Core or
NCI drivers which already behave asynchronously.
Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: Use system_nrt_wq instead of custom ones2012-09-24T22:17:23+00:00Tejun Heotj@kernel.org2012-08-22T23:22:16+00:00urn:sha1:474fee3db16c63bc440bfb93b57f72ecfc4246f0
NFC is using a number of custom ordered workqueues w/ WQ_MEM_RECLAIM.
WQ_MEM_RECLAIM is unnecessary unless NFC is gonna be used as transport
for storage device, and all use cases match one work item to one
ordered workqueue - IOW, there's no actual ordering going on at all
and using system_nrt_wq gives the same behavior.
There's nothing to be gained by using custom workqueues. Use
system_nrt_wq instead and drop all the custom ones.
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: Add target mode protocols to the polling loop startup routine2012-06-04T19:34:29+00:00Samuel Ortizsameo@linux.intel.com2012-05-15T13:57:06+00:00urn:sha1:fe7c580073280c15bb4eb4f82bf20dddc1a68383
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: Add HCI/SHDLC support to let driver check for tag presence2012-05-15T21:28:00+00:00Eric Lapuyadeeric.lapuyade@intel.com2012-05-07T10:31:16+00:00urn:sha1:1676f75159c8091e865c33b61ad4934dfd3b7821
Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
NFC: SHDLC implementation2012-04-12T19:10:35+00:00Eric Lapuyadeeric.lapuyade@intel.com2012-04-10T17:43:07+00:00urn:sha1:eb738fe535ae8e44402c372ecc1321eee0552a09
Most NFC HCI chipsets actually use a simplified HDLC link layer to
carry HCI payloads.
This implementation registers itself as an HCI device on behalf of the
NFC driver.
Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>