NFC: digital: Ensure no DID in NFC-DEP responses
authorMark A. Greer <mgreer@animalcreek.com>
Tue, 23 Sep 2014 23:38:04 +0000 (16:38 -0700)
committerSamuel Ortiz <sameo@linux.intel.com>
Fri, 28 Nov 2014 11:38:10 +0000 (12:38 +0100)
commit3bc3f88af5328d369ff399d90f13c566d925c245
treec13ad10c66d7af92cf0ccbbe32ac0ac2e8d29849
parent6ce306682f7f07a5e9e51c655764ead214ef3869
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>
net/nfc/digital_dep.c
This page took 0.02559 seconds and 5 git commands to generate.