22 Apr, 2014
2 commits
-
Fixes a null pointer exception occurring when the IRQ request in
pn544_hci_i2c_probe fails and no platform data is available.Signed-off-by: Clément Perrochaud
Signed-off-by: Samuel Ortiz -
Add functions to recover hardware resources from the device-tree when not
provided by the platform data.Signed-off-by: Clément Perrochaud
Signed-off-by: Samuel Ortiz
17 Feb, 2014
2 commits
-
PN544 C3 firmwares already contain the command frames to be sent, but as
they may exceed the i2c maximum payload, we need to fragment them into
secure chunks and send them through the secure write command.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
Different pn544 hardware variant may use different commands to download
new firmwares. The C2 does a regular firmware download while the C3 uses
a more secure protocol.
As a consequence we need to pass the hardware variant from the HCI SW
version command reply down to the pn544 i2c layer, in order to use the
right protocol at run time.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz
04 Jan, 2014
1 commit
-
Some of the EEPROM configurations that are assigned by the PN544 driver
are set by the firmware and should not be modified by the driver. Others
are certain user mode configurations that are currently getting set to values
that shouldn't necessarily be dictated by the driver. This patch changes
most user and system mode configurations to the firmware defaults.Signed-off-by: Arman Uguray
Signed-off-by: Samuel Ortiz
11 Dec, 2013
1 commit
-
Several files refer to an old address for the Free Software Foundation
in the file header comment. Resolve by replacing the address with
the URL so that we do not have to keep
updating the header comments anytime the address changes.CC: linux-wireless@vger.kernel.org
CC: Lauro Ramos Venancio
CC: Aloisio Almeida Jr
CC: Samuel Ortiz
Signed-off-by: Jeff Kirsher
Signed-off-by: John W. Linville
25 Sep, 2013
3 commits
-
Use standardized styles to minimize coding defects.
Always use nfc_ where feasible.
Add \n to formats where appropriate.
Typo "it it" correction.
Add #define pr_fmt where appropriate.
Remove function tracing logging messages.
Remove OOM messages.Signed-off-by: Joe Perches
Signed-off-by: Samuel Ortiz -
To enable the UICC secure element, we first enable the UICC gate list in
order for the SE to be able to use all RF technologies.
For the embedded SE, we just turn the eSE default mode to ON.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
For the SWP secure element, we send the proprietary SELF_TEST_SWP
command and check the response.
For the WI secure element, we simply try to switch to the default
embedded SE mode. If that works, it means we have an embedded SE.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz
14 Aug, 2013
3 commits
-
The pn544 can enter a firmware update mode where firmware blobs can be
pushed through the i2c line and flashed on the target.
A special command allows to verify that blobs are correctly flashed and
this is what we do for every downloaded firmware blob.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
The firmware operation callback is passed by the physical layer to the
hci driver during probe. All the driver does is to store it and call it
when the fw_upload hci ops is invoked.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
This is in preparation for pn544-i2c firmware download feature, where we
need to know if we're in regular or firmware upload mode.Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz
14 Jun, 2013
3 commits
-
Supported secure elements are typically found during a discovery process
initiated when the NFC controller is up and running. For a given NFC
chipset there can be many configurations (embedded SE or not, with or
without a SIM card wired to the NFC controller SWP interface, etc...) and
thus driver code will never know before hand which SEs are available.
So we remove this field, it will be replaced by a real SE discovery
mechanism.Signed-off-by: Samuel Ortiz
-
There is no builtin command for driver to check the presence of
Felica and Jewel device, it is more reasonable for the userspace
daemon neard to build seperate commands to check the presence of
the card.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz -
NFCID2 is defined as the first 2 manufacturer ID (IDm) bytes.
NFC DEP (NFC peer to peer) devices Type-F NFCID2 must start with
0x01fe according to the NFC Digital Specification.
By checking those first 2 bytes we send the right command either to the
reader gate when NFCID2 != 0x1fe (The NFC tag case) or to the NFCIP1 gate
when seeing an NFC DEP device (The NFC peer to peer case).Without this fix, Felica (Type F) tags are not properly detected with this
driver.Signed-off-by: Arron Wang
Signed-off-by: Samuel Ortiz
21 May, 2013
2 commits
-
Enabling and disabling device is exclusively handled by the mei_phy_ops.
Signed-off-by: Samuel Ortiz
-
The callback registration starts a waiting read, so it needs to be fired
everytime the device is enabled. Otherwise following writes will never get
an answer back.Signed-off-by: Samuel Ortiz
16 Apr, 2013
1 commit
-
With the new mei_phy NFC driver API, the pn544 MEI physical layer is
minimal and similar to the microread one.Signed-off-by: Samuel Ortiz
29 Jan, 2013
1 commit
-
…wireless-next into for-davem
10 Jan, 2013
8 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
-
Signed-off-by: Samuel Ortiz
-
The pn544 init routine does nothing but adding the driver to the i2c bus.
Signed-off-by: Samuel Ortiz
-
As we may need to support other physical layers, we can avoid linking the
core part into each and every pn544 module.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 -
Signed-off-by: Eric Lapuyade
Signed-off-by: Samuel Ortiz -
Some chips use a standard HCI event code, destined to a proprietary
gate, with a different meaning. Therefore, the HCI driver must always
have a chance to intercept the event before standard processing is
attempted.
The new semantic specifies that the result value "1" means that the
driver doesn't especially handle the event. result
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
04 Jan, 2013
1 commit
-
CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
markings need to be removed.This change removes the use of __devinit, __devexit_p, __devinitdata,
__devinitconst, and __devexit from these drivers.Based on patches originally written by Bill Pemberton, but redone by me
in order to handle some of the coding style issues better, by hand.Cc: Bill Pemberton
Signed-off-by: Greg Kroah-Hartman
20 Nov, 2012
1 commit
-
The pn544.h just provides the platform data struct and defines and
nothing else. So move it to to linux/platform_data/ now.Signed-off-by: Marcel Holtmann
Signed-off-by: Samuel Ortiz
27 Oct, 2012
2 commits
-
Signed-off-by: Arron Wang
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