From: Sanchayan Maity <maitysanchayan@gmail.com>
To: arnd@arndb.de, linux-arm-kernel@lists.infradead.org
Cc: stefan@agner.ch, shawn.guo@linaro.org, kernel@pengutronix.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v3 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes
Date: Fri, 22 May 2015 16:21:53 +0530 [thread overview]
Message-ID: <958427d37a2e4ca8fd60d7f150a22299abfed127.1432290463.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1432290463.git.maitysanchayan@gmail.com>
In-Reply-To: <cover.1432290463.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 | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 2f4b04d..66c529f 100644
--- a/arch/arm/boot/dts/vfxxx.dtsi
+++ b/arch/arm/boot/dts/vfxxx.dtsi
@@ -57,6 +57,11 @@
interrupt-parent = <&mscm_ir>;
ranges;
+ ocrom: ocrom {
+ compatible = "fsl,vf610-ocrom", "syscon";
+ reg = <0x00000000 0x18000>;
+ };
+
aips0: aips-bus@40000000 {
compatible = "fsl,aips-bus", "simple-bus";
#address-cells = <1>;
@@ -403,6 +408,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-22 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 10:51 [PATCH v3 0/2] Implement SoC bus support for Vybrid Sanchayan Maity
2015-05-22 10:51 ` Sanchayan Maity [this message]
2015-05-22 10:51 ` [PATCH v3 2/2] soc: Add driver for Freescale Vybrid Platform Sanchayan Maity
2015-05-22 11:11 ` Arnd Bergmann
2015-05-22 11:55 ` maitysanchayan
2015-05-22 12:02 ` Stefan Agner
2015-05-22 13:20 ` Arnd Bergmann
2015-05-25 10:17 ` maitysanchayan
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=958427d37a2e4ca8fd60d7f150a22299abfed127.1432290463.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®