From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Stefan Agner <stefan@agner.ch>,
Fabio Estevam <fabio.estevam@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: [PATCH 1/6] dt-bindings: crypto: Add Freescale Vybrid CRC
Date: Thu, 30 Aug 2018 19:15:34 +0200 [thread overview]
Message-ID: <20180830171539.20008-2-krzk@kernel.org> (raw)
In-Reply-To: <20180830171539.20008-1-krzk@kernel.org>
Add bindings for Freescale/NXP Vybrid CRC HW accelerator.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
.../devicetree/bindings/crypto/fsl-vf610-crc.txt | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/fsl-vf610-crc.txt
diff --git a/Documentation/devicetree/bindings/crypto/fsl-vf610-crc.txt b/Documentation/devicetree/bindings/crypto/fsl-vf610-crc.txt
new file mode 100644
index 000000000000..cdd7e26baeac
--- /dev/null
+++ b/Documentation/devicetree/bindings/crypto/fsl-vf610-crc.txt
@@ -0,0 +1,16 @@
+Freescale/NXP Vybrid VF500/VF610 CRC HW accelerator
+
+Required properties:
+- compatible : Should be "fsl,vf610-crc"
+- reg : Should contain register location and length.
+- clocks : Should contain the clock driving the CRC block.
+- clock-names : Should be set to "crc".
+
+Example:
+
+crc@40033000 {
+ compatible = "fsl,vf610-crc";
+ reg = <0x40033000 0x10>;
+ clocks = <&clks VF610_CLK_CRC>;
+ clock-names = "crc";
+};
--
2.14.1
next prev parent reply other threads:[~2018-08-30 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 17:15 [PATCH 0/6] crypto: vf-crc - Add new driver (and required clk, DTS...) Krzysztof Kozlowski
2018-08-30 17:15 ` Krzysztof Kozlowski [this message]
2018-08-30 17:15 ` [PATCH 2/6] clk: imx: vf610: Add CRC clock Krzysztof Kozlowski
2018-08-30 21:42 ` Stephen Boyd
2018-08-30 17:15 ` [PATCH 3/6] ARM: dts: vfxxx: Add node for CRC hardware block Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 4/6] crypto: testmgr - Add CRC16 test tables Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 5/6] crypto - Group Freescale/NXP ARM architecture Kconfig entires together Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 6/6] crypto: vf-crc - Add new driver for Freescale Vybrid CRC Krzysztof Kozlowski
2018-08-31 7:39 ` Sascha Hauer
2018-08-31 11:07 ` Krzysztof Kozlowski
2018-08-31 13:36 ` Sascha Hauer
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=20180830171539.20008-2-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).