From: Tero Kristo <t-kristo@ti.com>
To: <linux-omap@vger.kernel.org>, <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] ARM: dts: dra7: add PRM nodes
Date: Wed, 28 Aug 2019 10:56:36 +0300 [thread overview]
Message-ID: <20190828075644.4493-3-t-kristo@ti.com> (raw)
In-Reply-To: <20190828075644.4493-1-t-kristo@ti.com>
Add PRM nodes for dra7 series of SoCs. These are initially used to
support reset control for some of the nodes, but will be extended
later to add powerdomain control and support for PRCM irqs among
other things.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
---
arch/arm/boot/dts/dra7.dtsi | 55 +++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 953f0ffce2a9..95147289be9c 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -763,3 +763,58 @@
#include "dra7-l4.dtsi"
#include "dra7xx-clocks.dtsi"
+
+&prm {
+ prm_dsp1: prm@400 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x400 0x100>;
+ #reset-cells = <1>;
+ clocks = <&dsp1_clkctrl DRA7_DSP1_MMU0_DSP1_CLKCTRL 0>;
+ };
+
+ prm_ipu: prm@500 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x500 0x100>;
+ #reset-cells = <1>;
+ clocks = <&ipu1_clkctrl DRA7_IPU1_MMU_IPU1_CLKCTRL 0>;
+ };
+
+ prm_core: prm@700 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x700 0x100>;
+ #reset-cells = <1>;
+ clocks = <&ipu2_clkctrl DRA7_IPU2_MMU_IPU2_CLKCTRL 0>;
+ };
+
+ prm_iva: prm@f00 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0xf00 0x100>;
+ };
+
+ prm_dsp2: prm@1b00 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x1b00 0x40>;
+ #reset-cells = <1>;
+ clocks = <&dsp2_clkctrl DRA7_DSP2_MMU0_DSP2_CLKCTRL 0>;
+ };
+
+ prm_eve1: prm@1b40 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x1b40 0x40>;
+ };
+
+ prm_eve2: prm@1b80 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x1b80 0x40>;
+ };
+
+ prm_eve3: prm@1bc0 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x1bc0 0x40>;
+ };
+
+ prm_eve4: prm@1c00 {
+ compatible = "ti,dra7-prm-inst";
+ reg = <0x1c00 0x60>;
+ };
+};
--
2.17.1
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-28 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:56 [PATCH 00/10] ARM: dts: omap changes for IOMMU / reset support Tero Kristo
2019-08-28 7:56 ` [PATCH 01/10] ARM: dts: omap5: add IVA clkctrl nodes Tero Kristo
2019-08-28 7:56 ` Tero Kristo [this message]
2019-08-28 7:56 ` [PATCH 03/10] ARM: dts: omap4: add PRM nodes Tero Kristo
2019-08-28 7:56 ` [PATCH 04/10] ARM: dts: am33xx: Add PRM data Tero Kristo
2019-08-28 7:56 ` [PATCH 05/10] ARM: dts: am43xx: " Tero Kristo
2019-08-28 7:56 ` [PATCH 06/10] ARM: dts: omap5: " Tero Kristo
2019-08-28 7:56 ` [PATCH 07/10] ARM: dts: dra7: convert IOMMUs to use ti-sysc Tero Kristo
2019-08-28 7:56 ` [PATCH 08/10] ARM: dts: dra74x: " Tero Kristo
2019-08-28 7:56 ` [PATCH 09/10] ARM: dts: omap4: " Tero Kristo
2019-08-28 7:56 ` [PATCH 10/10] ARM: dts: omap5: " Tero Kristo
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=20190828075644.4493-3-t-kristo@ti.com \
--to=t-kristo@ti.com \
--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).