From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] crypto/fsl - disable RNG oscillator maximum frequency check
Date: Tue, 4 Aug 2015 08:51:56 -0700 [thread overview]
Message-ID: <55C0DF9C.2070208@freescale.com> (raw)
In-Reply-To: <1430833715-18193-2-git-send-email-alexandru.porosanu@freescale.com>
On 05/05/2015 06:48 AM, Alex Porosanu wrote:
> The rtfrqmax & rtfrqmin set the bounds of the expected frequency of the
> oscillator, when SEC runs at its maximum frequency. For certain platforms
> (f.i. T2080), the oscillator is very fast and thus if the SEC runs at
> a lower than normal frequency, the ring oscillator is incorrectly detected
> as being out of bounds.
>
> This patch effectively disables the maximum frequency check, by setting a
> high enough maximum allowable frequency for the oscillator. The reasoning
> behind this is that usually a broken oscillator will run too slow
> (i.e. not run at all) rather than run too fast.
>
> Signed-off-by: Alex Porosanu <alexandru.porosanu@freescale.com>
> ---
Applied to u-boot-fsl-qoriq master with minor change in subject. Thanks.
York
next prev parent reply other threads:[~2015-08-04 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 13:48 [U-Boot] [PATCH 0/3] CAAM RNG fixes Alex Porosanu
2015-05-05 13:48 ` [U-Boot] [PATCH 1/3] crypto/fsl - disable RNG oscillator maximum frequency check Alex Porosanu
[not found] ` <55AACF55.2030509@freescale.com>
2015-07-22 16:37 ` Ruchika Gupta
2015-08-04 15:51 ` York Sun [this message]
2015-05-05 13:48 ` [U-Boot] [PATCH 2/3] crypto/fsl - change starting entropy delay value Alex Porosanu
[not found] ` <55AACF57.8080105@freescale.com>
2015-07-22 16:37 ` Ruchika Gupta
2015-08-04 15:52 ` York Sun
2015-05-05 13:48 ` [U-Boot] [PATCH 3/3] crypto/fsl - enable raw data instead of von Neumann data Alex Porosanu
[not found] ` <55AACF69.8080904@freescale.com>
2015-07-22 16:37 ` Ruchika Gupta
2015-08-04 15:52 ` York Sun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C0DF9C.2070208@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.