From: Dan Murphy <dmurphy@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Cc: tony@atomide.com, Dan Murphy <dmurphy@ti.com>
Subject: [v3 PATCH 3/6] ARM: dts: am33xx: Add prcm_resets node
Date: Thu, 17 Jul 2014 11:45:28 -0500 [thread overview]
Message-ID: <1405615531-15649-3-git-send-email-dmurphy@ti.com> (raw)
In-Reply-To: <1405615531-15649-1-git-send-email-dmurphy@ti.com>
Add the prcm_resets node to the prcm parent node.
Add the am33xx_resets file to define the
am33xx reset lines that are handled by this reset
framework.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
v3 - No changes
arch/arm/boot/dts/am33xx-resets.dtsi | 42 ++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 7 ++++++
2 files changed, 49 insertions(+)
create mode 100644 arch/arm/boot/dts/am33xx-resets.dtsi
diff --git a/arch/arm/boot/dts/am33xx-resets.dtsi b/arch/arm/boot/dts/am33xx-resets.dtsi
new file mode 100644
index 0000000..9260626
--- /dev/null
+++ b/arch/arm/boot/dts/am33xx-resets.dtsi
@@ -0,0 +1,42 @@
+/*
+ * Device Tree Source for AM33XX reset data
+ *
+ * Copyright (C) 2014 Texas Instruments, Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+&prcm_resets {
+ gfx_rstctrl {
+ reg = <0x1104>,
+ <0x1114>;
+
+ gfx_reset: gfx_reset {
+ control-bit = <0x01>;
+ status-bit = <0x01>;
+ };
+ };
+
+ per_rstctrl {
+ reg = <0xD00>,
+ <0xD0C>;
+
+ iva_reset: iva_reset {
+ control-bit = <0x04>;
+ status-bit = <0x10>;
+ };
+ };
+
+ device_rstctrl {
+ reg = <0xf00>,
+ <0xf08>;
+
+ device_reset: device_reset {
+ control-bit = <0x01>;
+ status-bit = <0x01>;
+ };
+ };
+
+};
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 4a4e02d..5cdc8f0 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -117,6 +117,12 @@
prcm_clockdomains: clockdomains {
};
+
+ prcm_resets: resets {
+ #address-cells = <1>;
+ #size-cells = <1>;
+ #reset-cells = <1>;
+ };
};
scrm: scrm@44e10000 {
@@ -834,3 +840,4 @@
};
/include/ "am33xx-clocks.dtsi"
+/include/ "am33xx-resets.dtsi"
--
1.7.9.5
next prev parent reply other threads:[~2014-07-17 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 16:45 [v3 PATCH 1/6] drivers: reset: TI: SoC reset controller support Dan Murphy
2014-07-17 16:45 ` [v3 PATCH 2/6] dt: TI: Describe the ti reset DT entries Dan Murphy
2014-07-21 7:01 ` Tony Lindgren
2014-07-22 18:51 ` Suman Anna
2014-07-17 16:45 ` Dan Murphy [this message]
2014-07-22 18:54 ` [v3 PATCH 3/6] ARM: dts: am33xx: Add prcm_resets node Suman Anna
2014-07-17 16:45 ` [v3 PATCH 4/6] ARM: dts: am4372: " Dan Murphy
2014-07-22 19:01 ` Suman Anna
[not found] ` <1405615531-15649-1-git-send-email-dmurphy-l0cyMroinI0@public.gmane.org>
2014-07-17 16:45 ` [v3 PATCH 5/6] ARM: dts: dra7: Add prm_resets node Dan Murphy
2014-07-22 19:07 ` Suman Anna
2014-07-17 16:45 ` [v3 PATCH 6/6] ARM: dts: omap5: " Dan Murphy
2014-07-22 19:09 ` Suman Anna
2014-07-18 6:41 ` [v3 PATCH 1/6] drivers: reset: TI: SoC reset controller support Lothar Waßmann
2014-07-22 20:16 ` Suman Anna
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=1405615531-15649-3-git-send-email-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).