diff options
| author | Mark A. Greer <mgreer@animalcreek.com> | 2014-09-23 16:38:04 -0700 |
|---|---|---|
| committer | Samuel Ortiz <sameo@linux.intel.com> | 2014-11-28 12:38:10 +0100 |
| commit | 3bc3f88af5328d369ff399d90f13c566d925c245 (patch) | |
| tree | c13ad10c66d7af92cf0ccbbe32ac0ac2e8d29849 /include | |
| parent | 6ce306682f7f07a5e9e51c655764ead214ef3869 (diff) | |
| download | linux-stable-3bc3f88af5328d369ff399d90f13c566d925c245.tar.gz linux-stable-3bc3f88af5328d369ff399d90f13c566d925c245.tar.bz2 linux-stable-3bc3f88af5328d369ff399d90f13c566d925c245.zip | |
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>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions