From: Tomer Maimon <tmaimon77@gmail.com>
To: <avifishman70@gmail.com>, <tali.perry1@gmail.com>,
<joel@jms.id.au>, <venture@google.com>, <yuenn@google.com>,
<benjaminfair@google.com>, <olivia@selenic.com>,
<herbert@gondor.apana.org.au>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
Tomer Maimon <tmaimon77@gmail.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] rng: npcm: add Arbel NPCM8XX support
Date: Thu, 29 Sep 2022 16:31:09 +0300 [thread overview]
Message-ID: <20220929133111.73897-1-tmaimon77@gmail.com> (raw)
This patch set adds Arbel NPCM8XX Random Number Generator(RNG) support
to RNG NPCM driver.
The NPCM8XX RNG uses different prescalar clock value.
The NPCM RNG driver was tested on the NPCM845 evaluation board.
Addressed comments from:
- Krzysztof Kozlowski: https://www.spinics.net/lists/kernel/msg4523771.html
https://www.spinics.net/lists/kernel/msg4523585.html
Changes since version 1:
- Fix dt-binding document warning.
- Use driver data to handle architecture specific clock prescaler.
Tomer Maimon (2):
dt-bindings: rng: nuvoton,npcm-rng: Add npcm845 compatible string
hwrng: npcm: Add NPCM8XX support
.../devicetree/bindings/rng/nuvoton,npcm-rng.yaml | 4 +++-
drivers/char/hw_random/npcm-rng.c | 14 ++++++++++----
2 files changed, 13 insertions(+), 5 deletions(-)
--
2.33.0
next reply other threads:[~2022-09-29 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 13:31 Tomer Maimon [this message]
2022-09-29 13:31 ` [PATCH v2 1/2] dt-bindings: rng: nuvoton,npcm-rng: Add npcm845 compatible string Tomer Maimon
2022-09-29 13:31 ` [PATCH v2 2/2] hwrng: npcm: Add NPCM8XX support Tomer Maimon
2022-10-21 11:34 ` [PATCH v2 0/2] rng: npcm: add Arbel " Herbert Xu
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=20220929133111.73897-1-tmaimon77@gmail.com \
--to=tmaimon77@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).