From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andre Przywara <andre.przywara@arm.com>,
Ard Biesheuvel <ardb@kernel.org>
Cc: Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
Ali Saidi <alisaidi@amazon.com>,
Jon Nettleton <jon@solid-run.com>
Subject: Re: [PATCH v2] hwrng: Add Arm SMCCC TRNG based driver
Date: Wed, 21 Jul 2021 08:02:42 +1000 [thread overview]
Message-ID: <e494866f38e9dcd2834971d3867244fb1d7e6ceb.camel@kernel.crashing.org> (raw)
In-Reply-To: <20210720171631.071f84f5@slackpad.fritz.box>
On Tue, 2021-07-20 at 17:16 +0100, Andre Przywara wrote:
> Yes, a similar idea was already brought up before. I think there is even
> the potential for something like an artificial SMCCC "bus", where those
> services presentable as devices could be auto-detected (by checking
> known function IDs), the respective drivers would then probe
> automatically?
Sounds like a boot time killer... can we instead describe them in DT
and/or ACPI ?
Cheers,
Ben.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-20 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 15:21 [PATCH v2] hwrng: Add Arm SMCCC TRNG based driver Andre Przywara
2021-07-20 16:03 ` Ard Biesheuvel
2021-07-20 16:16 ` Andre Przywara
2021-07-20 22:02 ` Benjamin Herrenschmidt [this message]
2021-07-20 23:18 ` Andre Przywara
2021-07-21 11:16 ` Mark Brown
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=e494866f38e9dcd2834971d3867244fb1d7e6ceb.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alisaidi@amazon.com \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jon@solid-run.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=will@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).