From: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-coco@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@nvidia.com>,
Greg KH <gregkh@linuxfoundation.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Will Deacon <will@kernel.org>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Subject: Re: [PATCH v12 2/7] firmware: hwrng: arm_smccc_trng: Register as an SMCCC device
Date: Mon, 21 Sep 2026 14:31:24 +0530 [thread overview]
Message-ID: <yq5acxu73rmj.fsf@kernel.org> (raw)
In-Reply-To: <arDuqtfrRcBmWRic@arm.com>
Catalin Marinas <catalin.marinas@arm.com> writes:
> On Mon, Sep 21, 2026 at 11:08:02AM +0530, Aneesh Kumar K.V (Arm) wrote:
>> The SMCCC TRNG interface is a firmware-provided SMCCC service rather than a
>> standalone platform device. Now that the SMCCC core has an SMCCC bus,
>> create an arm-smccc-trng device for the discovered TRNG service and convert
>> the hwrng driver to an SMCCC driver.
>>
>> The SMCCC id table preserves module autoloading for systems where the TRNG
>> driver is built as a module.
>>
>> The sysfs device path changes from the old smccc_trng platform-device path
>> to an arm-smccc device path. No known userspace dependency on the old path
>> was found; a Debian Code Search lookup for the existing platform-device
>> name/path did not find any users.
>>
>> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>> Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
>> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
>> Tested-by: Andre Przywara <andre.przywara@arm.com>
>> Signed-off-by: Aneesh Kumar K.V (Arm) <aneesh.kumar@kernel.org>
>> ---
>> arch/arm/include/asm/archrandom.h | 2 +-
>> arch/arm64/include/asm/archrandom.h | 2 +-
>> drivers/char/hw_random/arm_smccc_trng.c | 32 ++++++++-----
>> drivers/firmware/smccc/smccc.c | 62 +++++++++++++++++++++----
>> 4 files changed, 76 insertions(+), 22 deletions(-)
>
> I asked you two times already to cc the hw_random maintainers. Not
> adding them again but not merging this stuff without their ack either.
> So, up to you.
>
Sorry, I missed that. I'll repost and Cc the hw_random maintainers.
-aneesh
next prev parent reply other threads:[~2026-09-21 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 5:38 [PATCH v12 0/7] Switch Arm SMCCC firmware services to an SMCCC bus Aneesh Kumar K.V (Arm)
2026-09-21 5:38 ` [PATCH v12 1/7] firmware: smccc: Add an Arm " Aneesh Kumar K.V (Arm)
2026-09-21 8:39 ` Catalin Marinas
2026-09-21 9:03 ` Aneesh Kumar K.V
2026-09-21 5:38 ` [PATCH v12 2/7] firmware: hwrng: arm_smccc_trng: Register as an SMCCC device Aneesh Kumar K.V (Arm)
2026-09-21 8:45 ` Catalin Marinas
2026-09-21 9:01 ` Aneesh Kumar K.V [this message]
2026-09-21 5:38 ` [PATCH v12 3/7] firmware: arm_rmm: Move RSI support out of arch/arm64 Aneesh Kumar K.V (Arm)
2026-09-21 8:50 ` Catalin Marinas
2026-09-21 5:38 ` [PATCH v12 4/7] arm64: realm: Move Realm memory encryption ops to RSI code Aneesh Kumar K.V (Arm)
2026-09-21 8:52 ` Catalin Marinas
2026-09-21 9:05 ` Aneesh Kumar K.V
2026-09-21 10:00 ` Suzuki K Poulose
2026-09-21 22:24 ` Jonathan Cameron
2026-09-21 5:38 ` [PATCH v12 5/7] virt: coco: arm-cca-guest: Rename TSM report source file Aneesh Kumar K.V (Arm)
2026-09-21 22:25 ` Jonathan Cameron
2026-09-21 5:38 ` [PATCH v12 6/7] firmware: smccc: arm-cca-guest: Bind the TSM provider to an SMCCC device Aneesh Kumar K.V (Arm)
2026-09-21 5:38 ` [PATCH v12 7/7] coco: guest: arm64: Replace dummy CCA device with sysfs ABI Aneesh Kumar K.V (Arm)
2026-09-21 9:00 ` Catalin Marinas
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=yq5acxu73rmj.fsf@kernel.org \
--to=aneesh.kumar@kernel.org \
--cc=Suzuki.Poulose@arm.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.linton@arm.com \
--cc=jgg@nvidia.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®