linux-kernel - Re: [PATCH v2] hwrng: Add Arm SMCCC TRNG based driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 21 Jul 2021 08:02:42 +1000
From:   Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:     Andre Przywara <andre.przywara@....com>,
        Ard Biesheuvel <ardb@...nel.org>
Cc:     Matt Mackall <mpm@...enic.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>, Will Deacon <will@...nel.org>,
        Ali Saidi <alisaidi@...zon.com>,
        Jon Nettleton <jon@...id-run.com>
Subject: Re: [PATCH v2] hwrng: Add Arm SMCCC TRNG based driver

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.