kernel.git/Documentation/devicetree/bindings/net/nfc, branch linux-4.2.yHosts the 0x221E linux distro kernel.
https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.2.y2015-06-11T21:41:57ZNFC: nfcmrvl: add UART driver2015-06-11T21:41:57ZVincent Cuissard2015-06-11T12:00:20Zurn:sha1:e097dc624f784debbde49701a493bf920bc422c7
Add support of Marvell NFC chip controlled over UART
Signed-off-by: Vincent Cuissard <cuissard@marvell.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
nfc: st-nci: Rename st21nfcb to st-nci2015-06-10T10:51:44ZChristophe Ricard2015-06-09T20:26:05Zurn:sha1:ed06aeefdac348cfb91a3db5fe1067e3202afd70
STMicroelectronics NFC NCI chips family is extending
with the new ST21NFCC using the AMS AS39230 RF booster.
The st21nfcb driver is relevant for this solution and
might be with future products.
Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: trf7970a: Handle extra byte in response to Type 5 RMB commands2015-06-08T21:16:31ZMark A. Greer2015-04-24T17:37:22Zurn:sha1:ab714817d7e891608d31f6996b1e4c43cf2bf342
The current versions of the trf7970a has an erratum where it returns
an extra byte in the response to 'Read Multiple Block' (RMB) commands.
This command is issued to Type 5 tags (i.e., ISO/IEC 15693 tags) by
the neard daemon.
To handle this, define a new Device Tree property,
't5t-rmb-extra-byte-quirk', which indicates that the associated
trf7970a device has this erratum. The trf7970a device driver
will then ensure that the response length to RMB commands is
reduced by one byte (for devices with the erratum).
Signed-off-by: Mark A. Greer <mgreer@animalcreek.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: nxp-nci_i2c: Add I2C support to NXP NCI driver2015-03-26T10:21:41ZClément Perrochaud2015-03-09T10:12:05Zurn:sha1:6be88670fc59d50426f90f734a36b90e1de7d148
Add a module to the NXP-NCI driver to support NFC controllers with an
I2C control interface, such as the NPC100.
Signed-off-by: Clément Perrochaud <clement.perrochaud@effinnov.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: dts: st21nfca: Document ese-present & uicc-present DTS property2015-01-27T23:03:37ZChristophe Ricard2015-01-27T00:18:20Zurn:sha1:3b060532621ef52e9e58c7596868c2570229a47b
On st21nfca, the mechanism to enable a secure element needs to add 2
properties in order manage the SWP line correctly.
Document ese-present and uicc-present properties.
Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: dts: st21nfcb: Fix compatible string spelling to follow other drivers2015-01-25T23:09:22ZChristophe Ricard2014-12-08T21:08:07Zurn:sha1:1a94cb6025d49bb28fd3d639b59e296b19771069
Other drivers are following the following compatible string format for dts:
s/_/-/
Because some devices may still use the previous string, the new corrected
string is added to the of_device_id table.
Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: dts: st21nfca: Fix compatible string spelling to follow other drivers2015-01-25T23:09:22ZChristophe Ricard2014-12-08T21:08:06Zurn:sha1:6b5fba4eb4267bb8025538f43aac4af51151c890
Other drivers are following the following compatible string format for dts:
s/_/-/
Because some devices may still use the previous string, the new corrected
string is added to the of_device_id table.
Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: dts: st21nfcb_i2c: Fix invalid interrupts polarity.2014-09-24T00:02:23ZChristophe Ricard2014-09-13T08:28:46Zurn:sha1:f06d87a5b5a01fced0493651a12c002906d0bb69
St21nfcb has a reverse polarity compare to st21nfca.
In st21nfcb case, the irq pin is active high.
Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: trf7970a: Document the 'en2-rf-quirk' DT property2014-08-31T22:06:56ZMark A. Greer2014-08-08T00:41:46Zurn:sha1:6afed0eb8c4158c99845f8d30cd5c3fd8e4855d9
Current versions of the trf7970a have an erratum where
the EN2 pin must be kept low. If it isn't kept low,
it will generate an RF field even when in passive
target mode. To work around this issue, create the
'en2-rf-quirk' device tree property to indicate that
the trf7970a that the driver is using has this erratum.
Signed-off-by: Mark A. Greer <mgreer@animalcreek.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
NFC: trf7970a: Document the 'irq-status-read-quirk' DT property2014-08-31T22:06:55ZMark A. Greer2014-08-08T00:41:44Zurn:sha1:d953ada493711363d5b7f2151100c242923fc56b
The mechanism for specifying that the trf7970a
being used by the driver has the "IRQ Status Read"
erratum has been changed to a device tree property
('irq-status-read-quirk').
Document the new device tree property.
Signed-off-by: Mark A. Greer <mgreer@animalcreek.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>