From: maitysanchayan@gmail.com (Sanchayan Maity)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver
Date: Wed, 12 Aug 2015 18:49:21 +0530 [thread overview]
Message-ID: <24fcfdc695907103e8f4602b7dc6b8fa38e85ec1.1439384645.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1439384645.git.maitysanchayan@gmail.com>
Add the devicetree bindings for the Freescale Vybrid On-Chip
OTP driver.
Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
.../devicetree/bindings/nvmem/vf610-ocotp.txt | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
diff --git a/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
new file mode 100644
index 0000000..b29f65f
--- /dev/null
+++ b/Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
@@ -0,0 +1,21 @@
+On-Chip OTP Memory for Freescale Vybrid
+
+Required Properties:
+ compatible:
+ - "fsl,vf610-ocotp" for VF5xx/VF6xx
+ #address-cells : Should be 1
+ #size-cells : Should be 1
+ reg : Address and length of OTP controller and fuse map registers
+ clocks : ipg clock we associate with the OCOTP peripheral
+ clock-names : Must contain "ocotp" as matching entry
+
+Example for Vybrid VF5xx/VF6xx:
+
+ ocotp: ocotp at 400a5000 {
+ compatible = "fsl,vf610-ocotp";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ reg = <0x400a5000 0xCF0>;
+ clocks = <&clks VF610_CLK_OCOTP>;
+ clock-names = "ocotp";
+ };
--
2.5.0
next prev parent reply other threads:[~2015-08-12 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:19 [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-09-06 8:15 ` Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com
2015-08-12 13:19 ` [PATCH v9 2/4] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-08-12 13:19 ` [PATCH v9 3/4] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-08-12 13:19 ` Sanchayan Maity [this message]
2015-09-06 8:13 ` [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver Shawn Guo
2015-09-06 10:28 ` maitysanchayan at gmail.com
2015-08-24 8:32 ` [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM maitysanchayan at gmail.com
2015-09-04 5:50 ` maitysanchayan at gmail.com
2015-09-04 8:21 ` Srinivas Kandagatla
2015-09-04 8:21 ` maitysanchayan at gmail.com
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=24fcfdc695907103e8f4602b7dc6b8fa38e85ec1.1439384645.git.maitysanchayan@gmail.com \
--to=maitysanchayan@gmail.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).