From: Richard van Schagen <vschagen@icloud.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
matthias.bgg@gmail.com, robh+dt@kernel.org
Cc: linux-crypto@vger.kernel.org, Richard van Schagen <vschagen@icloud.com>
Subject: [PATCH v3 1/2] dt-bindings: crypto: Add Mediatek EIP-93 crypto engine
Date: Wed, 27 Oct 2021 17:13:28 +0800 [thread overview]
Message-ID: <20211027091329.3093641-2-vschagen@icloud.com> (raw)
In-Reply-To: <20211027091329.3093641-1-vschagen@icloud.com>
Add bindings for the Mediatek EIP-93 crypto engine.
Signed-off-by: Richard van Schagen <vschagen@icloud.com>
---
Changes since V2:
- Adding 2 missing "static" which got lost in my editing (sorry)
Changes since V1
- Add missing #include to examples
.../bindings/crypto/mediatek,mtk-eip93.yaml | 43 +++++++++++++++++++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/mediatek,mtk-eip93.yaml
diff --git a/Documentation/devicetree/bindings/crypto/mediatek,mtk-eip93.yaml b/Documentation/devicetree/bindings/crypto/mediatek,mtk-eip93.yaml
new file mode 100644
index 000000000..422870afb
--- /dev/null
+++ b/Documentation/devicetree/bindings/crypto/mediatek,mtk-eip93.yaml
@@ -0,0 +1,43 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/crypto/mediatek,mtk-eip93.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Mediatek EIP93 crypto engine
+
+maintainers:
+ - Richard van Schagen <vschagen@icloud.com>
+
+properties:
+ compatible:
+ enum:
+ - mediatek, mtk-eip93
+
+ reg:
+ maxItems: 1
+
+ interrupts-parent:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupt-parent
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/mips-gic.h>
+
+ crypto: crypto@1e004000 {
+ compatible = "mediatek,mtk-eip93";
+ reg = <0x1e004000 0x1000>;
+ interrupt-parent = <&gic>;
+ interrupts = <GIC_SHARED 19 IRQ_TYPE_LEVEL_HIGH>;
+ };
--
2.30.2
next prev parent reply other threads:[~2021-10-27 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 9:13 [PATCH v3 0/2] Enable the Mediatek EIP-93 crypto engine Richard van Schagen
2021-10-27 9:13 ` Richard van Schagen [this message]
2021-10-27 13:58 ` [PATCH v3 1/2] dt-bindings: crypto: Add " Rob Herring
2021-10-27 9:13 ` [PATCH v3 2/2] crypto: mtk-eip93 - " Richard van Schagen
2021-10-28 5:12 ` kernel test robot
2021-10-28 6:27 ` kernel test robot
2021-10-29 6:41 ` Richard van Schagen
2021-10-28 7:49 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 1:58 [PATCH v3 1/2] dt-bindings: crypto: " Richard van Schagen
2021-11-02 17:37 ` Rob Herring
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=20211027091329.3093641-2-vschagen@icloud.com \
--to=vschagen@icloud.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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