From: Oscar A Perez <linux@neuralgames.com>
To: Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Oscar A Perez <linux@neuralgames.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] hwrng: Add support for ASPEED RNG
Date: Mon, 20 Jan 2020 15:01:08 +0000 [thread overview]
Message-ID: <20200120150113.2565-1-linux@neuralgames.com> (raw)
This minimal driver adds support for the Hardware Random Number Generator
that comes with the AST2400/AST2500/AST2600 SOCs from AspeedTech.
The HRNG on these SOCs uses Ring Oscillators working together to generate
a stream of random bits that can be read by the platform via a 32bit data
register.
Signed-off-by: Oscar A Perez <linux@neuralgames.com>
---
.../devicetree/bindings/rng/aspeed-rng.yaml | 90 +++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rng/aspeed-rng.yaml
diff --git a/Documentation/devicetree/bindings/rng/aspeed-rng.yaml b/Documentation/devicetree/bindings/rng/aspeed-rng.yaml
new file mode 100644
index 000000000000..06070ebe1c33
--- /dev/null
+++ b/Documentation/devicetree/bindings/rng/aspeed-rng.yaml
@@ -0,0 +1,90 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/rng/aspeed-rng.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+
+title: Bindings for Aspeed Hardware Random Number Generator
+
+
+maintainers:
+ - Oscar A Perez <linux@neuralgames.com>
+
+
+description: |
+ The HRNG on the AST2400/AST2500/AST2600 SOCs from AspeedTech uses four Ring
+ Oscillators working together to generate a stream of random bits that can be
+ read by the platform via a 32bit data register every one microsecond.
+ All the platform has to do is to provide to the driver the 'quality' entropy
+ value, the 'mode' in which the combining ROs will generate the stream of
+ random bits and, the 'period' value that is used as a wait-time between reads
+ from the 32bit data register.
+
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - enum:
+ - aspeed,ast2400-rng
+ - aspeed,ast2500-rng
+ - aspeed,ast2600-rng
+
+
+ reg:
+ description:
+ Base address and length of the register set of this block.
+ Currently 'reg' must be eight bytes wide and 32-bit aligned.
+
+ maxItems: 1
+
+
+ period:
+ description:
+ Wait time in microseconds to be used between reads.
+ The RNG on these Aspeed SOCs generates 32bit of random data
+ every one microsecond. Choose between 1 and n microseconds.
+
+ maxItems: 1
+
+
+ mode:
+ description:
+ One of the eight modes in which the four internal ROs (Ring
+ Oscillators) are combined to generate a stream of random
+ bits. The default mode is seven which is the default method
+ of combining RO random bits on these Aspeed SOCs.
+
+ maxItems: 1
+
+
+ quality:
+ description:
+ Estimated number of bits of entropy per 1024 bits read from
+ the RNG. Note that the default quality is zero which stops
+ this HRNG from automatically filling the kernel's entropy
+ pool with data.
+
+ maxItems: 1
+
+
+required:
+ - compatible
+ - reg
+ - period
+ - quality
+
+
+examples:
+ - |
+ rng: hwrng@1e6e2074 {
+ compatible = "aspeed,ast2500-rng";
+ reg = <0x1e6e2074 0x8>;
+ period = <4>;
+ quality = <128>;
+ mode = <0x7>;
+ };
+
+
+...
--
2.17.1
next reply other threads:[~2020-01-20 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 15:01 Oscar A Perez [this message]
2020-01-20 15:01 ` [PATCH 2/2] hwrng: Add support for ASPEED RNG Oscar A Perez
2020-01-20 19:21 ` kbuild test robot
2020-01-21 1:53 ` [PATCH 1/2] " Joel Stanley
2020-01-23 1:25 ` linux
2020-01-23 1:53 ` Andrew Jeffery
2020-01-25 1:10 ` linux
2020-01-28 0:53 ` Andrew Jeffery
2020-01-29 0:26 ` linux
2020-02-03 4:07 ` Andrew Jeffery
2020-02-03 4:09 ` Andrew Jeffery
2020-02-03 10:31 ` Rob Herring
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=20200120150113.2565-1-linux@neuralgames.com \
--to=linux@neuralgames.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).