10 Jan, 2013
4 commits
-
Each NFC adapter can have several links to different secure elements and
that property needs to be exported by the drivers.
A secure element link can be enabled and disabled, and card emulation will
be handled by the currently active one. Otherwise card emulation will be
host implemented.Signed-off-by: Samuel Ortiz
-
Some chips diverge from the HCI spec in their implementation of standard
features. This adds a new quirks parameter to
nfc_hci_allocate_device() to let the driver indicate its divergence.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
There is no use to return an error if the caller doesn't get it.
Signed-off-by: Samuel Ortiz
-
When an adapter is removed, it will unregister itself from hci and/or
nfc core. In order to do that safely, work tasks must first be canceled
and prevented to be scheduled again, before the hci or nfc device can be
destroyed.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
20 Nov, 2012
2 commits
-
Some HCI drivers will need it.
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
27 Oct, 2012
6 commits
-
As a consequence the NFC device IDs won't be increasing all the time,
as IDR provides the first available ID.Signed-off-by: Samuel Ortiz
-
The driver now has all HCI stuff isolated in one file, and all the
hardware link specifics in another. Writing a pn544 driver on top of
another hardware link is now just a matter of adding a new file for that
new hardware specifics.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
And implement the corresponding hooks for pn544.
Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
And implement the corresponding hooks for pn544.
Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
Set the local general bytes and default value for NFCIP1
Target/Initiator registries if the protocol is NFC-DEPSigned-off-by: Arron Wang
Signed-off-by: Samuel Ortiz
28 Sep, 2012
1 commit
-
…wireless-next into for-davem
Conflicts:
net/nfc/netlink.cSigned-off-by: John W. Linville <linville@tuxdriver.com>
25 Sep, 2012
11 commits
-
xmit callback provided by a driver encapsulates upper layers
data and sends it to the hardware. So, HCI does not know the
exact amount of data being sent and thus can't handle partially
sent frames properly.Therefore, the driver must return 0 for completely sent frame or
negative for failure.Signed-off-by: Waldemar Rymarkiewicz
Acked-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
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
Signed-off-by: Samuel Ortiz -
This is used by HCI drivers such as the one for the pn544 which require
communications between HCI and the chip to use shdlc.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
This is a passthrough llc. It can be used by HCI drivers that don't
need link layer control. HCI will then write directly to the driver, and
driver will deliver incoming frames directly to HCI without any
processing.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
The LLC layer manages modules that control the link layer protocol (such
as shdlc) between HCI and an HCI driver. The driver must simply specify
the required llc when it registers with HCI.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
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
Signed-off-by: Samuel Ortiz -
This method initiates execution of an HCI cmd. Result will be delivered
through an asynchronous callback.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
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
Signed-off-by: Samuel Ortiz -
During NFC-DEP target activation, store the remote
general bytes to be used later in dep_link_up.
When dep_link_up is called, activate the NFC-DEP target,
and forward the remote general bytes.
When dep_link_down is called, deactivate the target.Signed-off-by: Ilan Elias
Signed-off-by: Samuel Ortiz -
Signed-off-by: Ilan Elias
Signed-off-by: Samuel Ortiz -
If initiator protocol is NFC-DEP, set the local general bytes
in nci_start_poll.Signed-off-by: Ilan Elias
Signed-off-by: Samuel Ortiz
11 Sep, 2012
1 commit
-
It is a frequent mistake to confuse the netlink port identifier with a
process identifier. Try to reduce this confusion by renaming fields
that hold port identifiers portid instead of pid.I have carefully avoided changing the structures exported to
userspace to avoid changing the userspace API.I have successfully built an allyesconfig kernel with this change.
Signed-off-by: "Eric W. Biederman"
Acked-by: Stephen Hemminger
Signed-off-by: David S. Miller
10 Jul, 2012
3 commits
-
Some NFC chips will statically create and open pipes for both standard
and proprietary gates. The driver can now pass this information to HCI
such that HCI will not attempt to create and open them, but will instead
directly use the passed pipe ids.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
This API should be used by drivers, HCI, SHDLC or NCI stacks to report an
unrecoverable error.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
05 Jun, 2012
6 commits
-
This routine will be called by drivers whenever they receive data in target
mode. This should be unexpected events and as such should be handled by a
standalone API (i.e. not as a callback pointer from an existing API).Signed-off-by: Samuel Ortiz
-
And rename the initiator mode data exchange ops for consistency sake.
Signed-off-by: Samuel Ortiz
-
Signed-off-by: Samuel Ortiz
-
Userspace gets a netlink event upon target mode activation.
The LLCP layer is also signaled when we get an ATR_REQ in order to get
the remote general bytes.Signed-off-by: Samuel Ortiz
-
Signed-off-by: Samuel Ortiz
-
Signed-off-by: Samuel Ortiz
16 May, 2012
5 commits
-
The NFC core code already does that for them.
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
Signed-off-by: John W. Linville -
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
Signed-off-by: John W. Linville -
It is now specified that nfc_target_found() and nfc_target_lost() core
functions must not be called from an atomic context. This allow us to
serialize calls and protect the targets table using the nfc device lock
instead of a spinlock.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
Signed-off-by: John W. Linville -
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
Signed-off-by: John W. Linville -
The NFC Core now caches the active nfc target pointer, thereby avoiding
the need to lookup the target table for each invocation of a driver ops.
Consequently, pn533, HCI and NCI now directly receive an nfc_target
pointer instead of a target index.Cc: Ilan Elias
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
Signed-off-by: John W. Linville
19 Apr, 2012
1 commit
-
…wireless-next into for-davem
Conflicts:
drivers/net/wireless/iwlwifi/iwl-testmode.c
include/net/nfc/nfc.h
net/nfc/netlink.c
net/wireless/nl80211.c