From: fabien.dessenne@st.com (Fabien Dessenne)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dt-bindings: Document STM32 CRYP bindings
Date: Thu, 13 Jul 2017 11:59:38 +0200 [thread overview]
Message-ID: <1499939979-8623-3-git-send-email-fabien.dessenne@st.com> (raw)
In-Reply-To: <1499939979-8623-1-git-send-email-fabien.dessenne@st.com>
Document device tree bindings for the STM32 CRYP.
Signed-off-by: Fabien Dessenne <fabien.dessenne@st.com>
---
.../devicetree/bindings/crypto/st,stm32-cryp.txt | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt
diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt b/Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt
new file mode 100644
index 0000000..f631c37
--- /dev/null
+++ b/Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt
@@ -0,0 +1,20 @@
+* STMicroelectronics STM32 CRYP
+
+Required properties:
+- compatible: Should be "st,stm32f756-cryp".
+- reg: The address and length of the peripheral registers space
+- clocks: The input clock of the CRYP instance
+- interrupts: The CRYP interrupts
+
+Optional properties:
+- resets: The input reset of the CRYP instance
+
+Example:
+cryp1: cryp at 50060000 {
+ compatible = "st,stm32f756-cryp";
+ reg = <0x50060000 0x400>;
+ interrupts = <79>;
+ clocks = <&rcc 0 STM32F7_AHB2_CLOCK(CRYP)>;
+ resets = <&rcc STM32F7_AHB2_RESET(CRYP)>;
+ status = "disabled";
+};
--
2.7.4
next prev parent reply other threads:[~2017-07-13 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 9:59 [PATCH 0/3] STM32 CRYP crypto driver Fabien Dessenne
2017-07-13 9:59 ` [PATCH 1/3] crypto: engine - permit to enqueue aead_request Fabien Dessenne
2017-07-13 9:59 ` Fabien Dessenne [this message]
2017-07-17 17:49 ` [PATCH 2/3] dt-bindings: Document STM32 CRYP bindings Rob Herring
2017-07-13 9:59 ` [PATCH 3/3] crypto: stm32 - Support for STM32 CRYP crypto module Fabien Dessenne
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=1499939979-8623-3-git-send-email-fabien.dessenne@st.com \
--to=fabien.dessenne@st.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).