devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongsheng Wang <dongsheng.wang@freescale.com>
To: scottwood@freescale.com
Cc: devicetree@vger.kernel.org, alison.wang@freescale.com,
	Wang Dongsheng <dongsheng.wang@freescale.com>,
	robh+dt@kernel.org, jason.jin@freescale.com,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm/layerscape: add RCPM device tree support for ls1021a.
Date: Tue, 15 Sep 2015 16:55:39 +0800	[thread overview]
Message-ID: <1442307339-15225-2-git-send-email-dongsheng.wang@freescale.com> (raw)
In-Reply-To: <1442307339-15225-1-git-send-email-dongsheng.wang@freescale.com>

From: Wang Dongsheng <dongsheng.wang@freescale.com>

Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
---
*v2*: No changes.
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/dts/ls1021a.dtsi
index 973a496..deb1271 100644
--- a/arch/arm/boot/dts/ls1021a.dtsi
+++ b/arch/arm/boot/dts/ls1021a.dtsi
@@ -139,6 +139,7 @@
 			sdhci,auto-cmd12;
 			big-endian;
 			bus-width = <4>;
+			rcpm-wakeup = <&rcpm 0x00000080 0x0>;
 			status = "disabled";
 		};
 
@@ -186,6 +187,11 @@
 			};
 		};
 
+		rcpm: rcpm@1ee2000 {
+			compatible = "fsl,ls1021a-rcpm", "fsl,qoriq-rcpm-2.1";
+			reg = <0x0 0x1ee2000 0x0 0x10000>;
+		};
+
 		dspi0: dspi@2100000 {
 			compatible = "fsl,ls1021a-v1.0-dspi";
 			#address-cells = <1>;
@@ -287,6 +293,7 @@
 			interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
 			clocks = <&sysclk>;
 			clock-names = "ipg";
+			rcpm-wakeup = <&rcpm 0x0 0x40000000>;
 			status = "disabled";
 		};
 
-- 
2.1.0.27.g96db324

  reply	other threads:[~2015-09-15  8:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  8:55 [PATCH v2 1/2] fsl: Add binding for RCPM Dongsheng Wang
2015-09-15  8:55 ` Dongsheng Wang [this message]
2015-09-15 23:56 ` Scott Wood
2015-09-16  2:15   ` Wang Dongsheng
     [not found]     ` <SN1PR0301MB1616C48FB3D990BCA45289AB9D5B0-VLIetriUNobRRq1t3zq48ZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-09-16  2:19       ` Scott Wood
2015-09-16  2:30         ` Wang Dongsheng
     [not found]           ` <SN1PR0301MB161688E3AF527ADC76AB2B8F9D5B0-VLIetriUNobRRq1t3zq48ZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-09-16  2:31             ` Scott Wood
2015-09-16  2:35               ` Yuantian Tang
     [not found]                 ` <DM2PR03MB574196E1A0D55C185CE1B4BFA5B0-ufbTtyGzTTSgVhSfO4NrDOO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-09-16  2:37                   ` Scott Wood
2015-09-16  2:43                     ` Wang Dongsheng
2015-09-16  3:18                     ` Wang Dongsheng
     [not found]                       ` <SN1PR0301MB1616C6AB0EF4ACE4624865159D5B0-VLIetriUNobRRq1t3zq48ZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-09-16  4:13                         ` Scott Wood
2015-09-16  5:11                           ` Wang Dongsheng

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=1442307339-15225-2-git-send-email-dongsheng.wang@freescale.com \
    --to=dongsheng.wang@freescale.com \
    --cc=alison.wang@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jason.jin@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=scottwood@freescale.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).