diff options
| author | Mark A. Greer <mgreer@animalcreek.com> | 2014-09-03 02:12:25 +0400 |
|---|---|---|
| committer | Samuel Ortiz <sameo@linux.intel.com> | 2014-09-08 01:13:43 +0400 |
| commit | 38b4eb1f7fa87079a5a40f5d2ec4b5c0c7f14a4b (patch) | |
| tree | df78df662950aa0c4f1d92a06bce1148f63a8523 /crypto/rmd128.c | |
| parent | 4e64eff837fb682dfb2a1188fb036d75ec57375c (diff) | |
| download | linux-38b4eb1f7fa87079a5a40f5d2ec4b5c0c7f14a4b.tar.xz | |
NFC: trf7970a: Recalculate driver timeout values
Some of the timeout values used in the driver
are not long enough to handle worst-case scenarios
so they need to be recalculated.
The time to wait for the FIFO to drain past the
low-watermark is now 20 ms because it can take
around 14.35 ms to send 95 bytes (127 bytes in
full FIFO minus 32 bytes where the low-watermark
interrupt will fire). 95 bytes will take around
14.35 ms at 6.62 kbps (the lowest supported bit
rate used by ISO/IEC 15693) so 20 ms should be a
safe value.
The time to wait before issuing an EOF to complete
an ISO/IEC 15693 write or lock command is 40 ms--
20 ms to drain the FIFO and another 20 ms to ensure
the wait is long enough before sending an EOF.
Signed-off-by: Mark A. Greer <mgreer@animalcreek.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'crypto/rmd128.c')
0 files changed, 0 insertions, 0 deletions