From: Sanchayan Maity <maitysanchayan@gmail.com>
To: arnd@arndb.de, shawn.guo@linaro.org, kernel@pengutronix.de
Cc: stefan@agner.ch, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v4 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes
Date: Tue, 26 May 2015 17:06:46 +0530 [thread overview]
Message-ID: <242cf9cea5244a6d783928e1f4783dead2aa32d5.1432637313.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1432637313.git.maitysanchayan@gmail.com>
In-Reply-To: <cover.1432637313.git.maitysanchayan@gmail.com>
Add a device tree node for the On-Chip One Time Programmable
Controller (OCOTP) and the On-Chip ROM.
Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
---
arch/arm/boot/dts/vfxxx.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 2f4b04d..ed9b6b8 100644
--- a/arch/arm/boot/dts/vfxxx.dtsi
+++ b/arch/arm/boot/dts/vfxxx.dtsi
@@ -56,6 +56,13 @@
compatible = "simple-bus";
interrupt-parent = <&mscm_ir>;
ranges;
+ ocotp-cfg = <&ocotp 0x410 0x420>;
+ rom-revision = <&ocrom 0x80>;
+
+ ocrom: ocrom {
+ compatible = "fsl,vf610-ocrom", "syscon";
+ reg = <0x00000000 0x18000>;
+ };
aips0: aips-bus@40000000 {
compatible = "fsl,aips-bus", "simple-bus";
@@ -403,6 +410,11 @@
status = "disabled";
};
+ ocotp: ocotp@400a5000 {
+ compatible = "fsl,vf610-ocotp", "syscon";
+ reg = <0x400a5000 0x1000>;
+ };
+
snvs0: snvs@400a7000 {
compatible = "fsl,sec-v4.0-mon", "simple-bus";
#address-cells = <1>;
--
2.4.1
next prev parent reply other threads:[~2015-05-26 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 11:36 [PATCH v4 0/2] Implement SoC bus support for Vybrid Sanchayan Maity
2015-05-26 11:36 ` Sanchayan Maity [this message]
2015-05-26 11:36 ` [PATCH v4 2/2] soc: Add driver for Freescale Vybrid Platform Sanchayan Maity
2015-05-27 7:31 ` Paul Bolle
2015-05-27 13:07 ` maitysanchayan
2015-05-27 16:46 ` Paul Bolle
2015-05-27 17:28 ` Andreas Färber
2015-05-27 17:47 ` Joachim Eastwood
2015-05-27 21:42 ` Stefan Agner
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=242cf9cea5244a6d783928e1f4783dead2aa32d5.1432637313.git.maitysanchayan@gmail.com \
--to=maitysanchayan@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.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
all inboxes | Powered by JetHome®