summaryrefslogtreecommitdiffstats
path: root/drivers/crypto/caam
diff options
context:
space:
mode:
authorSunil Goutham <sgoutham@marvell.com>2021-10-29 19:19:59 +0200
committerHerbert Xu <herbert@gondor.apana.org.au>2021-11-20 05:02:07 +0100
commit680efb33546be8960ccbb2f4e0e43034d9c93b30 (patch)
treec935d527f94213541a3d280e668b7b2c3f705818 /drivers/crypto/caam
parentcrypto: atmel-aes - Reestablish the correct tfm context at dequeue (diff)
downloadlinux-680efb33546be8960ccbb2f4e0e43034d9c93b30.tar.xz
linux-680efb33546be8960ccbb2f4e0e43034d9c93b30.zip
hwrng: cavium - Check health status while reading random data
This RNG device is present on Marvell OcteonTx2 silicons as well and also provides entropy health status. HW continuously checks health condition of entropy and reports faults. Fault is in terms of co-processor cycles since last fault detected. This doesn't get cleared and only updated when new fault is detected. Also there are chances of detecting false positives. So to detect a entropy failure SW has to check if failures are persistent ie cycles elapsed is frequently updated by HW. This patch adds support to detect health failures using below algo. 1. Consider any fault detected before 10ms as a false positive and ignore. 10ms is chosen randomly, no significance. 2. Upon first failure detection make a note of cycles elapsed and when this error happened in realtime (cntvct). 3. Upon subsequent failure, check if this is new or a old one by comparing current cycles with the ones since last failure. cycles or time since last failure is calculated using cycles and time info captured at (2). HEALTH_CHECK status register is not available to VF, hence had to map PF registers. Also since cycles are in terms of co-processor cycles, had to retrieve co-processor clock rate from RST device. Signed-off-by: Sunil Goutham <sgoutham@marvell.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/caam')
0 files changed, 0 insertions, 0 deletions