From: Markus Mayer <mmayer@broadcom.com>
To: Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Aurelien Jarno <aurelien@aurel32.net>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Golle <daniel@makrotopia.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>
Cc: Markus Mayer <mmayer@broadcom.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] hwrng: bcm74110 - Add Broadcom BCM74110 RNG driver
Date: Wed, 30 Oct 2024 14:33:53 -0700 [thread overview]
Message-ID: <20241030213400.802264-1-mmayer@broadcom.com> (raw)
This series adds a driver for the random number generator found on the
BCM74110 SoC.
Markus Mayer (2):
dt-bindings: rng: add binding for BCM74110 RNG
hwrng: bcm74110 - Add Broadcom BCM74110 RNG driver
.../bindings/rng/brcm,bcm74110.yaml | 35 +++++
drivers/char/hw_random/Kconfig | 14 ++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/bcm74110-rng.c | 125 ++++++++++++++++++
4 files changed, 175 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rng/brcm,bcm74110.yaml
create mode 100644 drivers/char/hw_random/bcm74110-rng.c
--
2.46.0
next reply other threads:[~2024-10-30 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 21:33 Markus Mayer [this message]
2024-10-30 21:33 ` [PATCH 1/2] dt-bindings: rng: add binding for BCM74110 RNG Markus Mayer
2024-10-30 21:42 ` Florian Fainelli
2024-10-30 22:36 ` Rob Herring (Arm)
2024-10-31 7:29 ` Krzysztof Kozlowski
2024-10-31 18:55 ` Markus Mayer
2024-11-01 6:50 ` Krzysztof Kozlowski
2024-10-30 21:33 ` [PATCH 2/2] hwrng: bcm74110 - Add Broadcom BCM74110 RNG driver Markus Mayer
2024-10-30 21:41 ` Florian Fainelli
2024-10-31 18:35 ` Markus Mayer
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=20241030213400.802264-1-mmayer@broadcom.com \
--to=mmayer@broadcom.com \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=francesco.dolcini@toradex.com \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=robh@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).