From: James Hartley <james.hartley@imgtec.com>
To: <herbert@gondor.apana.org.au>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<galak@codeaurora.org>, <andrew.bresticker@chromium.org>,
<ezequiel.garcia@imgtec.com>
Cc: <linux-crypto@vger.kernel.org>, <james.hartley@imgtec.com>
Subject: [PATCH V3 2/2] Documentation: crypto: Add DT binding info for the img hw hash accelerator
Date: Fri, 6 Mar 2015 02:58:27 +0000 [thread overview]
Message-ID: <1425610707-9869-3-git-send-email-james.hartley@imgtec.com> (raw)
In-Reply-To: <1425610707-9869-1-git-send-email-james.hartley@imgtec.com>
This adds the binding documentation for the Imagination Technologies
hash accelerator that provides hardware acceleration for
SHA1/SHA224/SHA256/MD5 hashes. This hardware will be present in
the upcoming pistachio SoC.
Signed-off-by: James Hartley <james.hartley@imgtec.com>
---
.../devicetree/bindings/crypto/img-hash.txt | 27 ++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/img-hash.txt
diff --git a/Documentation/devicetree/bindings/crypto/img-hash.txt b/Documentation/devicetree/bindings/crypto/img-hash.txt
new file mode 100644
index 0000000..7adc519
--- /dev/null
+++ b/Documentation/devicetree/bindings/crypto/img-hash.txt
@@ -0,0 +1,27 @@
+Imagination Technologies hardware hash accelerator
+
+The hash accelerator provides hardware hashing acceleration for
+SHA1, SHA224, SHA256 and MD5 hashes
+
+Required properties:
+
+- compatible : "img,hash-accelerator"
+- reg : Offset and length of the register set for the module, and the DMA port
+- interrupts : The designated IRQ line for the hashing module.
+- dmas : DMA specifier as per Documentation/devicetree/bindings/dma/dma.txt
+- dma-names : Should be "tx"
+- clocks : Clock specifiers
+- clock-names : "hash_clk" Used to clock data through the accelerator
+ "hash_reg_clk" Used to clock the hash block registers
+
+Example:
+
+ hash: hash@18149600 {
+ compatible = "img,hash-accelerator";
+ reg = <0x18149600 0x100, 0x18101100 0x4>;
+ interrupts = <GIC_SHARED 59 IRQ_TYPE_LEVEL_HIGH>;
+ dmas = <&dma 8 0xffffffff>;
+ dma-names = "tx";
+ clocks = <&cr_periph SYS_CLK_HASH>, <&clk_periph PERIPH_CLK_ROM>;
+ clock-names = "hash_clk, hash_reg_clk";
+ };
--
1.7.9.5
next prev parent reply other threads:[~2015-03-06 2:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 2:58 [PATCH V3 0/2] Add support for the IMG hash accelerator James Hartley
2015-03-06 2:58 ` [PATCH V3 1/2] crypto: Add Imagination Technologies hw " James Hartley
2015-03-09 6:35 ` Stephan Mueller
2015-03-10 9:37 ` Herbert Xu
2015-03-10 9:53 ` James Hartley
2015-03-10 9:54 ` James Hartley
2015-03-10 9:55 ` Herbert Xu
2015-03-10 12:30 ` James Hartley
2015-03-06 2:58 ` James Hartley [this message]
[not found] <1425610912-9930-1-git-send-email-james.hartley@imgtec.com>
[not found] ` <1425610912-9930-3-git-send-email-james.hartley@imgtec.com>
2015-03-06 21:50 ` [PATCH V3 2/2] Documentation: crypto: Add DT binding info for the img " Andrew Bresticker
2015-03-10 15:34 ` James Hartley
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=1425610707-9869-3-git-send-email-james.hartley@imgtec.com \
--to=james.hartley@imgtec.com \
--cc=andrew.bresticker@chromium.org \
--cc=ezequiel.garcia@imgtec.com \
--cc=galak@codeaurora.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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