Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 143
    • Issues 143
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • Librem5
  • linux
  • Merge requests
  • !680

Draft: hack: crypto: caam - fix i.MX8MQ entropy delay value

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Martin Kepplinger requested to merge martin.kepplinger/linux-next:entropy_delay into pureos/byzantium Mar 15, 2023
  • Overview 2
  • Commits 1
  • Pipelines 1
  • Changes 1

Similar to commit 4ee4cdad ("crypto: caam - fix i.MX6SX entropy delay value") increase the delay (nr of system clock cycles) the RNG has to get 1 bit of entropy.

With the default value (3200) we see errors like: caam_jr 30902000.jr: 2000025b: CCB: desc idx 2: RNG: Hardware error

Vabhav wanted to adda DT property even, to make this more configurable: https://lore.kernel.org/linux-arm-kernel/20220530180924.1792399-1-vabhav.sharma@nxp.com/ which just would need finding a suitible format / physical unit. But in case the value from imx6sx is appropriate for imx8mq too, let's keep this oneliner.

Probably Fixes #467

3200 (clock cycles) is the default - apprearently too low. this uses 12000. Since NXP ran some tests and the imx6sx RNG is at least compatible with the imx8mq one (not sure if exactly the same), I'd suggest to use 12000. But we could as well test whether a lower value would be enough - but then again - how would we really know?

Edited Mar 17, 2023 by Martin Kepplinger
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: entropy_delay