From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: ansuelsmth@gmail.com, herbert@gondor.apana.org.au,
davem@davemloft.net, chester.a.unal@arinc9.com,
sergio.paracuellos@gmail.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, matthias.bgg@gmail.com,
tsbogend@alpha.franken.de,
angelogioacchino.delregno@collabora.com,
linux-crypto@vger.kernel.org, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: [PATCH 1/2] dt-bindings: crypto: Add support for Mediatek MT7621 SoC
Date: Thu, 1 Jan 2026 18:12:04 +0100 [thread overview]
Message-ID: <20260101171212.1861241-1-olek2@wp.pl> (raw)
Add compatible for Airoha AN7583 SoC. The implementation is exactly the
same os in the Airoha SoC.
Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
.../bindings/crypto/inside-secure,safexcel-eip93.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
index 997bf9717f9e..8ccff64f5c1c 100644
--- a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
+++ b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
@@ -33,6 +33,9 @@ properties:
- items:
- const: airoha,en7581-eip93
- const: inside-secure,safexcel-eip93ies
+ - items:
+ - const: mediatek,mt7621-eip93
+ - const: inside-secure,safexcel-eip93ies
- items:
- not: {}
description: Need a SoC specific compatible
--
2.47.3
next reply other threads:[~2026-01-01 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 17:12 Aleksander Jan Bajkowski [this message]
2026-01-01 17:12 ` [PATCH 2/2] mips: dts: ralink: mt7621: add crypto offload support Aleksander Jan Bajkowski
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=20260101171212.1861241-1-olek2@wp.pl \
--to=olek2@wp.pl \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=chester.a.unal@arinc9.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--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=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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