From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sean Wang <sean.wang@mediatek.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: rng: mtk-rng: add SMC-based TRNG variants
Date: Wed, 4 Mar 2026 13:18:20 +0100 [thread overview]
Message-ID: <8e685c37-afca-4f2e-ac0a-76a0b060805d@kernel.org> (raw)
In-Reply-To: <aagiPIgoosVqsA0t@makrotopia.org>
On 04/03/2026 13:14, Daniel Golle wrote:
>
> Starting with MT7981 and followed by MT7988 and MT7987 it is
> technically the same hardware, but on those ARMv8 SoCs TF-A assigns
So they are compatible, I presume?
> the MMIO range of the TRNG to only be accessible from within the
> secure/trusted land, and TF-A provides a (vendor-specific) API
> allowing non-trusted land (ie. Linux) to acquire random bytes.
>
> With MT7986 they made the unlucky choice to initially allow direct
> access to the MMIO range, but later updates to TF-A then also locked
> it to secure/trusted land, offering the same API as on the newer SoCs.
> So for MT7986 the driver has to try and figure out which convention to
> use.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-04 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 0:55 [PATCH 1/2] dt-bindings: rng: mtk-rng: add SMC-based TRNG variants Daniel Golle
2026-03-04 0:56 ` [PATCH 2/2] hwrng: mtk - add support for hw access via SMCC Daniel Golle
2026-03-04 11:34 ` [PATCH 1/2] dt-bindings: rng: mtk-rng: add SMC-based TRNG variants Krzysztof Kozlowski
2026-03-04 12:14 ` Daniel Golle
2026-03-04 12:18 ` Krzysztof Kozlowski [this message]
2026-03-04 12:21 ` Daniel Golle
2026-03-04 12:26 ` Krzysztof Kozlowski
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=8e685c37-afca-4f2e-ac0a-76a0b060805d@kernel.org \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=olivia@selenic.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.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