From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] m68k: coldfire: Add RNG support for MCF54418
Date: Thu, 06 Nov 2025 19:16:17 +0100 [thread overview]
Message-ID: <4689159.LvFx2qVVIh@jeanmichel-ms7b89> (raw)
In-Reply-To: <aQzHO6Ty+l1Bwt6N@lizhi-Precision-Tower-5810>
Hi Frank,
Le jeudi 6 novembre 2025, 17:05:15 heure normale d’Europe centrale Frank Li a
écrit :
> On Thu, Nov 06, 2025 at 08:10:08AM +0100, Jean-Michel Hautbois wrote:
> > Add platform device support for the MCF54418 RNGB hardware with clock
> > enabled at platform initialization.
> >
> > The imx-rngc driver now uses devm_clk_get_optional() to support both
> > Coldfire (always-on clock) and i.MX platforms (managed clock).
> >
> > Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
> > ---
> >
> > arch/m68k/coldfire/device.c | 28 ++++++++++++++++++++++++++++
> > arch/m68k/coldfire/m5441x.c | 2 +-
> > arch/m68k/include/asm/m5441xsim.h | 9 +++++++++
> > drivers/char/hw_random/Kconfig | 3 ++-
> > drivers/char/hw_random/imx-rngc.c | 9 ++++++++-
> > 5 files changed, 48 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/m68k/coldfire/device.c b/arch/m68k/coldfire/device.c
> > index
> > b6958ec2a220cf91a78a14fc7fa18749451412f7..9d8f844e319a98f0afb79cceb544c2d
> > 3029482a4 100644 --- a/arch/m68k/coldfire/device.c
> > +++ b/arch/m68k/coldfire/device.c
> > @@ -622,6 +622,31 @@ static struct platform_device mcf_flexcan0 = {
> >
> > };
> > #endif /* MCFFLEXCAN_SIZE */
> >
> > +#ifdef MCF_RNG_BASE
> > +/*
> > + * Random Number Generator (RNG) - only on MCF54418
> > + */
> > +static struct resource mcf_rng_resource[] = {
>
> const?
Why not, but I wanted to be consistent with all the other structures in this
file.
JM
> Frank
>
> > + {
> > + .start = MCF_RNG_BASE,
> > + .end = MCF_RNG_BASE + MCF_RNG_SIZE - 1,
> > + .flags = IORESOURCE_MEM,
> > + },
> > + {
> > + .start = MCF_IRQ_RNG,
> > + .end = MCF_IRQ_RNG,
> > + .flags = IORESOURCE_IRQ,
> > + },
> > +};
>
> ...
next prev parent reply other threads:[~2025-11-06 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 7:10 [PATCH] m68k: coldfire: Add RNG support for MCF54418 Jean-Michel Hautbois
2025-11-06 16:05 ` Frank Li
2025-11-06 18:16 ` Jean-Michel Hautbois [this message]
2025-11-06 19:25 ` Frank Li
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=4689159.LvFx2qVVIh@jeanmichel-ms7b89 \
--to=jeanmichel.hautbois@yoseli.org \
--cc=Frank.li@nxp.com \
--cc=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=olivia@selenic.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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