From: Mark A. Greer <mgreer@animalcreek.com>
Date: Tue, 23 Sep 2014 23:38:04 +0000 (-0700)
Subject: NFC: digital: Ensure no DID in NFC-DEP responses
X-Git-Tag: omap-for-v3.20/drop-legacy-3517~122^2~28^2~16^2~47
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3bc3f88af5328d369ff399d90f13c566d925c245;p=pandora-kernel.git

NFC: digital: Ensure no DID in NFC-DEP responses

When in Initiator mode, the digital layer's
NFC-DEP code always sets the Device ID (DID)
value in the ATR_REQ to '0'.  This means that
subsequent DEP_REQ and DEP_RES frames must
never include a DID byte.  This is specified
in sections 14.8.1.1 and 14.8.2.1 of the NFC
Digital Protocol Spec.

Currently, the digital layer's NFC-DEP code
doesn't enforce this rule so add code to ensure
that there is no DID byte in DEP_RES frames.

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>
---

Reading git-diff-tree failed