aboutsummaryrefslogtreecommitdiffstats
path: root/include/net/nfc
diff options
context:
space:
mode:
authorMark A. Greer <mgreer@animalcreek.com>2014-09-23 16:38:12 -0700
committerSamuel Ortiz <sameo@linux.intel.com>2014-11-28 12:39:47 +0100
commit49dbb14e30c3249f98fe243c3e21b91d10c5c59b (patch)
tree1d98889745d1c4d6ebf9150ef68a47dc762a693b /include/net/nfc
parentNFC: digital: Add NFC-DEP Initiator-side NACK Support (diff)
downloadlinux-dev-49dbb14e30c3249f98fe243c3e21b91d10c5c59b.tar.xz
linux-dev-49dbb14e30c3249f98fe243c3e21b91d10c5c59b.zip
NFC: digital: Add NFC-DEP Target-side NACK Support
When an NFC-DEP Target receives a NACK PDU with a PNI equal to 1 less than the current PNI, it is supposed to re-send the last PDU. This is implied in section 14.12.5.4 of the NFC Digital Protocol Spec. The digital layer's NFC-DEP code doesn't implement Target-side NACK handing so add it. The last PDU that was sent is saved in the 'nfc_digital_dev' structure's 'saved_skb' member. The skb will have an additional reference taken to ensure that the skb isn't freed when the driver performs a kfree_skb() on the skb. The length of the skb/PDU is also saved so the length can be restored when re-sending the PDU in the skb (the driver will perform an skb_pull() so an skb_push() needs to be done to restore the skb's data pointer/length). Reviewed-by: Thierry Escande <thierry.escande@linux.intel.com> Tested-by: Thierry Escande <thierry.escande@linux.intel.com> Signed-off-by: Mark A. Greer <mgreer@animalcreek.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'include/net/nfc')
-rw-r--r--include/net/nfc/digital.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/include/net/nfc/digital.h b/include/net/nfc/digital.h
index 2fd498cdb818..7400a8126cd1 100644
--- a/include/net/nfc/digital.h
+++ b/include/net/nfc/digital.h
@@ -235,6 +235,9 @@ struct nfc_digital_dev {
int nack_count;
+ struct sk_buff *saved_skb;
+ unsigned int saved_skb_len;
+
u16 target_fsc;
int (*skb_check_crc)(struct sk_buff *skb);