<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/net/nfc, branch v3.6</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.6</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2012-07-09T20:42:12Z</updated>
<entry>
<title>NFC: Allow HCI driver to pre-open pipes to some gates</title>
<updated>2012-07-09T20:42:12Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@linux.intel.com</email>
</author>
<published>2012-06-05T12:42:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a10d595b1074d04446f77161eea165e5809e163c'/>
<id>urn:sha1:a10d595b1074d04446f77161eea165e5809e163c</id>
<content type='text'>
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 &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Driver failure API</title>
<updated>2012-07-09T20:42:08Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@intel.com</email>
</author>
<published>2012-06-11T11:49:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=456411ca812860d7ba06d3e4013ce1d8b9dbc7cd'/>
<id>urn:sha1:456411ca812860d7ba06d3e4013ce1d8b9dbc7cd</id>
<content type='text'>
This API should be used by drivers, HCI, SHDLC or NCI stacks to report an
unrecoverable error.

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: Prepare asynchronous error management for driver and shdlc</title>
<updated>2012-07-09T20:42:04Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@intel.com</email>
</author>
<published>2012-04-30T16:21:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a9a741a7e2e6337ae5c030e78827c233c08902a7'/>
<id>urn:sha1:a9a741a7e2e6337ae5c030e78827c233c08902a7</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: Introduce target mode rx data callback</title>
<updated>2012-06-04T19:34:31Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-05-30T22:05:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=73167ced31d15c04e57b9e0885ac05675e9195a4'/>
<id>urn:sha1:73167ced31d15c04e57b9e0885ac05675e9195a4</id>
<content type='text'>
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 &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Introduce target mode tx ops</title>
<updated>2012-06-04T19:34:30Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-05-16T13:55:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=be9ae4ce4ee66e211815122ab4f41913efed4fec'/>
<id>urn:sha1:be9ae4ce4ee66e211815122ab4f41913efed4fec</id>
<content type='text'>
And rename the initiator mode data exchange ops for consistency sake.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Set the NFC device RF mode appropriately</title>
<updated>2012-06-04T19:34:30Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-05-30T22:02:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f212ad5e993e7efb996fc8ce94a5de8f0bd06d41'/>
<id>urn:sha1:f212ad5e993e7efb996fc8ce94a5de8f0bd06d41</id>
<content type='text'>
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Add target mode activation netlink event</title>
<updated>2012-06-04T19:34:30Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-06-01T11:21:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fc40a8c1a06ab7db45da790693dd9802612a055c'/>
<id>urn:sha1:fc40a8c1a06ab7db45da790693dd9802612a055c</id>
<content type='text'>
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 &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Add target mode protocols to the polling loop startup routine</title>
<updated>2012-06-04T19:34:29Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-05-15T13:57:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fe7c580073280c15bb4eb4f82bf20dddc1a68383'/>
<id>urn:sha1:fe7c580073280c15bb4eb4f82bf20dddc1a68383</id>
<content type='text'>
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Export LLCP general bytes getter</title>
<updated>2012-06-04T19:34:29Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2012-04-10T10:51:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ab73b751303bc60d7d9fba875c958dedfe14754c'/>
<id>urn:sha1:ab73b751303bc60d7d9fba875c958dedfe14754c</id>
<content type='text'>
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: HCI drivers don't have to keep track of polling state</title>
<updated>2012-05-15T21:31:22Z</updated>
<author>
<name>Eric Lapuyade</name>
<email>eric.lapuyade@intel.com</email>
</author>
<published>2012-05-07T10:31:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=03bed29e0501b5757ce62ebdb01829f7bd8d9819'/>
<id>urn:sha1:03bed29e0501b5757ce62ebdb01829f7bd8d9819</id>
<content type='text'>
The NFC core code already does that for them.

Signed-off-by: Eric Lapuyade &lt;eric.lapuyade@intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
