From: "Pali Rohár" <pali.rohar@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
"Paul Walmsley" <paul@pwsan.com>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Tony Lindgren" <tony@atomide.com>,
"Russell King" <linux@armlinux.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Tero Kristo" <t-kristo@ti.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"Adam Ford" <adam.ford@logicpd.com>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] ARM: omap3: Enable HWMODS for HW Random Number Generator
Date: Tue, 10 Sep 2019 18:39:06 +0200 [thread overview]
Message-ID: <20190910163906.ypyeaido6h4nurvv@pali> (raw)
In-Reply-To: <CAHCN7xLaGQMM67VC-2_G8XC7UuG4c+TbbYb4z=ibJwZsQF4YVw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]
On Tuesday 10 September 2019 11:21:34 Adam Ford wrote:
> According to a note in omap_hwmod_3xxx_data.c,
>
> /*
> * Apparently the SHA/MD5 and AES accelerator IP blocks are
> * only present on some AM35xx chips, and no one knows which
> * ones. See
> * http://www.spinics.net/lists/arm-kernel/msg215466.html So
> * if you need these IP blocks on an AM35xx, try uncommenting
> * the following lines.
> */
>
> I decided to uncomment the hwmod entries, and I got the following:
>
> [ 0.263222] omap_hwmod: sham: _wait_target_ready failed: -16
> [ 0.263248] omap_hwmod: sham: cannot be enabled for reset (3)
> [ 0.265837] omap_hwmod: aes: _wait_target_ready failed: -16
> [ 0.265851] omap_hwmod: aes: cannot be enabled for reset (3)
> [ 6.208866] omap_hwmod: sham: _wait_target_ready failed: -16
> [ 6.287732] omap_hwmod: aes: _wait_target_ready failed: -16
Hi! Same errors I got in qemu-n900, but not on real N900. So I guess
those errors means that IP blocks are not present.
> Based on this, I wonder if the sham and aes modules are not present.
> If this is the case, it might explain why I cannot use the rng either.
Probably this is the reason, you do not have crypto/rng HW engine.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-10 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 15:00 [RFC] ARM: omap3: Enable HWMODS for HW Random Number Generator Adam Ford
2019-09-05 23:04 ` Tony Lindgren
2019-09-09 12:13 ` Adam Ford
2019-09-09 13:37 ` Adam Ford
2019-09-09 13:40 ` Pali Rohár
2019-09-09 16:35 ` Tony Lindgren
2019-09-09 19:19 ` Adam Ford
2019-09-10 15:48 ` Adam Ford
2019-09-10 16:21 ` Adam Ford
2019-09-10 16:39 ` Pali Rohár [this message]
2019-10-22 12:13 ` Adam Ford
2019-10-22 16:06 ` Tony Lindgren
2019-09-10 13:56 ` Adam Ford
2019-09-10 14:37 ` Sebastian Reichel
2019-09-10 14:44 ` Pali Rohár
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=20190910163906.ypyeaido6h4nurvv@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=adam.ford@logicpd.com \
--cc=aford173@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=paul@pwsan.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox