summaryrefslogtreecommitdiffstats
path: root/mm/Kconfig.debug
diff options
context:
space:
mode:
authorAlex Porosanu <alexandru.porosanu@freescale.com>2014-08-11 11:40:16 +0300
committerHerbert Xu <herbert@gondor.apana.org.au>2014-08-25 20:32:35 +0800
commiteeaa1724a2e9c8958a8621b3c10d5ca0667e78fa (patch)
tree14853c2ae36391f4fa5f5aa55529e754a08f7488 /mm/Kconfig.debug
parentb061f3fefcffa0cdcdc61ae2a1123a4e7697d452 (diff)
downloadop-kernel-dev-eeaa1724a2e9c8958a8621b3c10d5ca0667e78fa.zip
op-kernel-dev-eeaa1724a2e9c8958a8621b3c10d5ca0667e78fa.tar.gz
crypto: caam - change starting entropy delay value
The entropy delay (the length in system clocks of each entropy sample) for the RNG4 block of CAAM is dependent on the frequency of the SoC. By elaborate methods, it has been determined that a good starting value for all platforms integrating the CAAM IP is 3200. Using a higher value has additional benefit of speeding up the process of instantiating the RNG, since the entropy delay will be increased and instantiation of the RNG state handles will be reattempted by the driver. If the starting value is low, for certain platforms, this can lead to a quite lengthy process. This patch changes the starting value of the length of the entropy sample to 3200 system clocks. In addition to this change, the attempted entropy delay values are now printed on the console upon initialization of the RNG block. While here, a safeguard for yielding the processor was added for ensuring that in very adverse cases, the CPU isn't hogged by the instantiation loop. Signed-off-by: Alex Porosanu <alexandru.porosanu@freescale.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'mm/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud