The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-samsung-soc@vger.kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: exynos-rng - Remove exynos-rng driver
Date: Wed, 10 Jun 2026 18:39:02 +0000	[thread overview]
Message-ID: <20260610183902.GA1158828@google.com> (raw)
In-Reply-To: <CADrjBPo3BpSk49oasf_9g06xrBMkw+NiKo10xDKjWr8sJ+Zc-Q@mail.gmail.com>

On Wed, Jun 10, 2026 at 03:46:54PM +0100, Peter Griffin wrote:
> Hi Eric,
> 
> On Sun, 31 May 2026 at 19:02, Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > This driver has no purpose.  It doesn't feed into the Linux RNG, nor
> > does it implement the hwrng interface.  It is accessible only via the
> > "rng" algorithm type of AF_ALG, which isn't used in practice.  Everyone
> > uses either the Linux RNG, or rarely /dev/hwrng.
> >
> > Moreover, this is a PRNG whose only source of entropy is the 160-bit
> > seed the user passes in.  So this can be used only by a user who already
> > has a source of cryptographically secure random numbers, such as
> > /dev/random.  Which they can, and do, just use in the first place.
> >
> > Just remove this driver.  There's no need to keep useless code around.
> >
> > Note that the other crypto_rng drivers in drivers/crypto/ are similarly
> > unused and are being removed too.  This commit just handles exynos-rng.
> >
> > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> > ---
> 
> If the driver is being removed, should the binding documentation for
> this driver not also be deleted (see
> Documentation/devicetree/bindings/rng/samsung,exynos4-rng.yaml)?
> 
> Peter

In other discussions I've been told that devicetree bindings are
hardware descriptions that should still exist even if there is no
driver.  It doesn't make a lot of sense, but it seems to be what the
devicetree people want.  I expect there would be objections to removing
this binding.

- Eric

  reply	other threads:[~2026-06-10 18:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 17:59 [PATCH] crypto: exynos-rng - Remove exynos-rng driver Eric Biggers
2026-06-01  9:39 ` Krzysztof Kozlowski
2026-06-10 14:46 ` Peter Griffin
2026-06-10 18:39   ` Eric Biggers [this message]
2026-06-11  7:11     ` Peter Griffin
2026-06-11  8:49 ` 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=20260610183902.GA1158828@google.com \
    --to=ebiggers@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzk@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.griffin@linaro.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