diff options
author | Eric Lapuyade <eric.lapuyade@linux.intel.com> | 2013-09-23 19:56:31 +0400 |
---|---|---|
committer | Samuel Ortiz <sameo@linux.intel.com> | 2013-09-25 16:25:41 +0400 |
commit | 22d4aae5897fb8355130b8f7d9a3af153eac9714 (patch) | |
tree | b11eb743ff1f9a816875b43237ae51f28695b421 /drivers/nfc/pn533.c | |
parent | a4ada6cadb8a2246f263ff6a0d0cca8832f3970e (diff) | |
download | linux-22d4aae5897fb8355130b8f7d9a3af153eac9714.tar.xz |
NFC: NCI: nci_spi_recv_frame() now returns (not forward) the read frame
Previously, nci_spi_recv_frame() would directly transmit incoming frames
to the NCI Core. However, it turns out that some NFC NCI Chips will add
additional proprietary headers that must be handled/removed before NCI
Core gets a chance to handle the frame. With this modification, the chip
phy or driver are now responsible to transmit incoming frames to NCI
Core after proper treatment, and NCI SPI becomes a driver helper instead
of sitting between the NFC driver and NCI Core.
As a general rule in NFC, *_recv_frame() APIs are used to deliver an
incoming frame to an upper layer. To better suit the actual purpose of
nci_spi_recv_frame(), and go along with its nci_spi_send()
counterpart, the function is renamed to nci_spi_read()
The skb is returned as the function result
Signed-off-by: Eric Lapuyade <eric.lapuyade@intel.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/nfc/pn533.c')
0 files changed, 0 insertions, 0 deletions