<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/nfc, branch v3.16</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/nfc?h=v3.16</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/nfc?h=v3.16'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-05-25T23:28:28Z</updated>
<entry>
<title>NFC: trf7970a: Add support for Felica Type 3 tags</title>
<updated>2014-05-25T23:28:28Z</updated>
<author>
<name>Mark A. Greer</name>
<email>mgreer@animalcreek.com</email>
</author>
<published>2014-04-14T17:04:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6857bb96271cd40ffb38825d43897d716310e3db'/>
<id>urn:sha1:6857bb96271cd40ffb38825d43897d716310e3db</id>
<content type='text'>
Add support for the Felica protocol and Type 3 tags.
Both 212 and 424 kbps are supported.

Signed-off-by: Mark A. Greer &lt;mgreer@animalcreek.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: port100: Add support for type 4B tag</title>
<updated>2014-05-25T22:42:02Z</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2014-04-11T22:03:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=09592ccfc2fc38eedd63f0f50fda095e1083b657'/>
<id>urn:sha1:09592ccfc2fc38eedd63f0f50fda095e1083b657</id>
<content type='text'>
This patch adds support for ISO-DEP protocol over NFC-B rf technology
by adding NFC_PROTO_ISO14443_B to the supported protocols and an entry
for framing configuration.

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Add ISO15693 Reader/Writer support</title>
<updated>2014-05-19T22:48:28Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-05-13T20:03:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7974728094d35f38775417a26d8f30ea3602496a'/>
<id>urn:sha1:7974728094d35f38775417a26d8f30ea3602496a</id>
<content type='text'>
Add support for ISO/IEC 15693 RF technology and Type 5 tags.
ISO15963 is using proprietary gate 12.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Improve load_session</title>
<updated>2014-05-19T22:48:06Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-05-13T20:03:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a779b8878c20a5cafff26d774eed4d36a903882a'/>
<id>urn:sha1:a779b8878c20a5cafff26d774eed4d36a903882a</id>
<content type='text'>
In case anybody uses previous patchset with the CLF, add a check to make sure
missing pipe are created.
st21nfca returns its pipe list in the creation order (most recent latest).

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: dts: st21nfca: Add device-tree (Open Firmware) support to st21nfca</title>
<updated>2014-05-19T22:47:43Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-05-13T20:03:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c44cb2edd01ca31471d9385f0895891b006ab904'/>
<id>urn:sha1:c44cb2edd01ca31471d9385f0895891b006ab904</id>
<content type='text'>
Add functions to recover hardware resources from the device-tree
when not provided by the platform data.

Based on pn544 devicetree implementation

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Free buffer when a bad frame is detected</title>
<updated>2014-05-04T23:04:10Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-04-24T21:19:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0c942b007b52cdcde285fa1122688f186bf99464'/>
<id>urn:sha1:0c942b007b52cdcde285fa1122688f186bf99464</id>
<content type='text'>
When a bad frame is detected for a bad crc.
We were reallocating and loosing the previous frame pointer.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Synchronize i2c Tx and Rx path</title>
<updated>2014-05-04T23:01:23Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-04-24T21:19:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a3c5d8fb7ffa8850f3d2fc01e1dde0709a3954f9'/>
<id>urn:sha1:a3c5d8fb7ffa8850f3d2fc01e1dde0709a3954f9</id>
<content type='text'>
Stabilize communication by using a mutex.
This avoids running a write transaction during a read retry or a read
transaction during a write retry.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Improved i2c Rx data correctness check</title>
<updated>2014-05-04T23:00:34Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-04-24T21:19:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c97ffdbf51ec3f944e6661ecb16985d47c8073c7'/>
<id>urn:sha1:c97ffdbf51ec3f944e6661ecb16985d47c8073c7</id>
<content type='text'>
A frame starts with ST21NFCA_SOF_EOF(0x7e) + 0x00.
A frame ends with ST21NFCA_SOF_EOF(0x7e).
It is possible that the i2c macrocell is stopped for other
communication interfaces with highest priority(RF or SWP).
This can be seen with some 0xFF data at the end of a received shdlc buffer.
If this happen we need to discard the frame because the CLF will repeat it.

In order to push accurate data to hci layer, we add the following fix:
- Instead of looking for the first 0x7e in the frame, check that the last
received byte is 0x7e.
- Check that the first frame reception block start with start of
frame(0x7e 0x00). If not, clear the buffer.
- Check that the next frame reception block do not start with start of
frame(0x7e). If so, clear the buffer.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Fix st21nfca_hci_remove_len_crc tail room handling</title>
<updated>2014-05-04T22:15:26Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-04-24T21:19:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1fb97b9256f383ed9553a1fc0b1576dfc88d582'/>
<id>urn:sha1:e1fb97b9256f383ed9553a1fc0b1576dfc88d582</id>
<content type='text'>
There is no byte stuffing when data are stored in skb.
TAILROOM is 2 byte crc + 1 byte eof.

st21nfca_hci_remove_len_crc was doing an incorrect operation on
the TAILROOM data.
If shdlc timer T2 is triggered, it will request to send the same data.
Before every hci data was lost after st21nfca_hci_remove_len_crc.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: st21nfca: Fix incorrect byte stuffing revocation</title>
<updated>2014-05-04T22:06:27Z</updated>
<author>
<name>Christophe Ricard</name>
<email>christophe.ricard@gmail.com</email>
</author>
<published>2014-04-24T21:19:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3096e25a3e40b73afd59e46f3bf8d84f919992a1'/>
<id>urn:sha1:3096e25a3e40b73afd59e46f3bf8d84f919992a1</id>
<content type='text'>
Byte stuffing was not correctly removed after a i2c read operation.
This was causing improper crc calculation when byte stuffing was
applied to more than 1 byte.

Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
</feed>
