<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/net/nfc, branch v3.10.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/net/nfc?h=v3.10.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/net/nfc?h=v3.10.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-04-12T14:54:45Z</updated>
<entry>
<title>NFC: RFKILL support</title>
<updated>2013-04-12T14:54:45Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2013-04-11T09:52:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=be055b2f89b5842f41363b5655a33dffb51a8294'/>
<id>urn:sha1:be055b2f89b5842f41363b5655a33dffb51a8294</id>
<content type='text'>
All NFC devices will now get proper RFKILL support as long as they provide
some dev_up and dev_down hooks. Rfkilling an NFC device will bring it down
while it is left to userspace to bring it back up when being rfkill unblocked.
This is very similar to what Bluetooth does.

Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Initial Secure Element API</title>
<updated>2013-01-09T23:51:54Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-12-19T18:11:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=390a1bd8538132186ddb679cafe9e75b7ef7e2d2'/>
<id>urn:sha1:390a1bd8538132186ddb679cafe9e75b7ef7e2d2</id>
<content type='text'>
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 &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Add HCI quirks to support driver (non)standard implementations</title>
<updated>2013-01-09T23:51:51Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-12-18T13:15:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bf71ab8ba53081c28b960d48e0c4cd1c17588aa6'/>
<id>urn:sha1:bf71ab8ba53081c28b960d48e0c4cd1c17588aa6</id>
<content type='text'>
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 &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Added error handling in event_received hci ops</title>
<updated>2013-01-09T23:51:49Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-11-28T14:48:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=27c31191b3d7ff32c266a5dbea344b9aa96ebf14'/>
<id>urn:sha1:27c31191b3d7ff32c266a5dbea344b9aa96ebf14</id>
<content type='text'>
There is no use to return an error if the caller doesn't get it.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Fixed nfc core and hci unregistration and cleanup</title>
<updated>2013-01-09T23:51:48Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-11-26T17:06:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f0c9103813b3045bd5b43220b6a78c9908a45d24'/>
<id>urn:sha1:f0c9103813b3045bd5b43220b6a78c9908a45d24</id>
<content type='text'>
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 &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Export nfc_hci_sak_to_protocol()</title>
<updated>2012-11-19T22:56:59Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-10-23T09:37:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9c5121a034b1414d83c553e9961bda823e2e65b4'/>
<id>urn:sha1:9c5121a034b1414d83c553e9961bda823e2e65b4</id>
<content type='text'>
Some HCI drivers will need it.

Signed-off-by: Eric Lapuyade &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Export nfc_hci_result_to_errno as it can be needed by HCI drivers</title>
<updated>2012-11-19T22:56:59Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-10-17T14:50:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=84d4819033972f6bae2b34a8ba07c5c2e836e989'/>
<id>urn:sha1:84d4819033972f6bae2b34a8ba07c5c2e836e989</id>
<content type='text'>
Signed-off-by: Eric Lapuyade &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Use IDR library to assing NFC devices IDs</title>
<updated>2012-10-26T16:26:51Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-10-22T13:57:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7eda8b8e967781cfa5a04962502f9aa428f67e5f'/>
<id>urn:sha1:7eda8b8e967781cfa5a04962502f9aa428f67e5f</id>
<content type='text'>
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 &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Separate pn544 hci driver in HW dependant and independant parts</title>
<updated>2012-10-26T16:26:46Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-10-02T16:44:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=97f18414af395c547f20300e5d4c81d7190a4155'/>
<id>urn:sha1:97f18414af395c547f20300e5d4c81d7190a4155</id>
<content type='text'>
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 &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Implement HCI DEP send and receive data</title>
<updated>2012-10-26T16:26:46Z</updated>
<author>
<name>Arron Wang</name>
<email>arron.wang@intel.com</email>
</author>
<published>2012-09-27T09:32:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e81076235b46189a776362ec5e4c6626bf1599ff'/>
<id>urn:sha1:e81076235b46189a776362ec5e4c6626bf1599ff</id>
<content type='text'>
And implement the corresponding hooks for pn544.

Signed-off-by: Arron Wang &lt;arron.wang@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
</feed>
