U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jamie.Gibbons--- via U-Boot" <u-boot@lists.u-boot-project.org>
To: <leo.liang@sifive.com>
Cc: <Valentina.FernandezAlanis@microchip.com>, <xypron.glpk@gmx.de>,
	<trini@konsulko.com>, <Conor.Dooley@microchip.com>,
	<sputnik@on-the-web.ch>, <u-boot@lists.u-boot-project.org>,
	<michal.simek@amd.com>, <u-boot@lists.denx.de>,
	<sughosh.ganu@arm.com>, <ycliang@andestech.com>
Subject: Re: [PATCH v2 3/6] rng: add Microchip PolarFire SoC hardware RNG driver
Date: Mon, 27 Jul 2026 08:12:37 +0000	[thread overview]
Message-ID: <5012bf190ba74c8467798efe7fd26bc53df19707.camel@microchip.com> (raw)
In-Reply-To: <CAC7DN2CW0VU3MBycsLzKoB0LztjC-DuVj1AbDYFFDPK4sMYxMA@mail.gmail.com>

Hi Leo,

On Mon, 2026-07-27 at 15:14 +0800, Leo Liang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> Hi Jamie,
> 
> On Thu, Jul 23, 2026 at 8:52 AM Jamie Gibbons
> <jamie.gibbons@microchip.com> wrote:
> > 
> > Add a U-Boot RNG driver for Microchip's PolarFire SoC (MPFS). The
> > hardware RNG is accessed indirectly via the MPFS system controller
> > using
> > the mailbox interface.
> > 
> > The driver implements the UCLASS_RNG interface, requesting random
> > data
> > from the system controller and returning it to the caller.
> > 
> > This allows use of the PolarFire SoC hardware RNG via the
> > standard 'rng' command and DM RNG API.
> > 
> > Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> > ---
> >  drivers/rng/Kconfig    |   7 +++
> >  drivers/rng/Makefile   |   1 +
> >  drivers/rng/mpfs_rng.c | 101
> > +++++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 109 insertions(+)
> >  create mode 100644 drivers/rng/mpfs_rng.c
> > 
> > diff --git a/drivers/rng/Kconfig b/drivers/rng/Kconfig
> > index 19b2b707677..856ffda2f5e 100644
> > --- a/drivers/rng/Kconfig
> > +++ b/drivers/rng/Kconfig
> > @@ -23,6 +23,13 @@ config RNG_MESON
> >           Enable support for hardware random number generator
> >           of Amlogic Meson SoCs.
> > 
> > +config RNG_MPFS
> > +       tristate "Microchip PolarFire SoC Random Number Generator
> > support"
> 
> Is there a special reason to use 'tristate' instead of 'bool'?
> If not, I could convert it to 'bool' when merging the patch,
> so you don't have to respin the patchset.

No, I don't believe there is a reason - this is a mistake. If you could
fix this on merge, that would be great.

Much appreciated,
Jamie.
> 
> Reviewed-by: Leo Yu-Chi Liang <leo.liang@sifive.com>
> 
> Best regards,
> Leo
> 
> > +       depends on DM_RNG && MPFS_SYSCONTROLLER
> > +       help
> > +         Enable support for hardware random number generator
> > +         of Microchip's PolarFire SoCs.
> > +


  reply	other threads:[~2026-07-27  9:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 15:45 [PATCH v2 0/6] MPFS: add hardware RNG support and fix RNG consumers Jamie Gibbons
2026-07-22 15:45 ` [PATCH v2 1/6] misc: mpfs_syscontroller: add mailbox RX helper for service responses Jamie Gibbons
2026-07-22 15:45 ` [PATCH v2 2/6] misc: mpfs_syscontroller: bind RNG sub-device Jamie Gibbons
2026-07-22 15:45 ` [PATCH v2 3/6] rng: add Microchip PolarFire SoC hardware RNG driver Jamie Gibbons
2026-07-27  7:14   ` Leo Liang via U-Boot
2026-07-27  8:12     ` Jamie.Gibbons--- via U-Boot [this message]
2026-07-28  7:59       ` Leo Liang via U-Boot
2026-07-22 15:45 ` [PATCH v2 4/6] configs: microchip_mpfs_generic: enable MPFS RNG support Jamie Gibbons
2026-07-27  7:14   ` Leo Liang via U-Boot
2026-07-22 15:45 ` [PATCH v2 5/6] mailbox: mpfs-mbox: replace unbounded BUSY polling with bounded waits Jamie Gibbons
2026-07-22 15:45 ` [PATCH v2 6/6] mailbox: mpfs: add bounded wait for BUSY to clear before sending request Jamie Gibbons
2026-07-28  8:12 ` [PATCH v2 0/6] MPFS: add hardware RNG support and fix RNG consumers Leo Liang via U-Boot

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=5012bf190ba74c8467798efe7fd26bc53df19707.camel@microchip.com \
    --to=u-boot@lists.u-boot-project.org \
    --cc=Conor.Dooley@microchip.com \
    --cc=Jamie.Gibbons@microchip.com \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=leo.liang@sifive.com \
    --cc=michal.simek@amd.com \
    --cc=sputnik@on-the-web.ch \
    --cc=sughosh.ganu@arm.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=ycliang@andestech.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