From: zyw@rock-chips.com (zyw at rock-chips.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: dts: add RK3288 suspend support
Date: Wed, 15 Oct 2014 13:49:04 -0700 [thread overview]
Message-ID: <1413406144-16329-1-git-send-email-zyw@rock-chips.com> (raw)
In-Reply-To: <1413405987-16196-1-git-send-email-zyw@rock-chips.com>
From: Chris Zhong <zyw@rock-chips.com>
add pmu_intmem subnode for suspend, add suspend pinctrl
Signed-off-by: Tony Xie <xxx@rock-chips.com>
Signed-off-by: Chris Zhong <zyw@rock-chips.com>
---
arch/arm/boot/dts/rk3288.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..081af7a 100644
--- a/arch/arm/boot/dts/rk3288.dtsi
+++ b/arch/arm/boot/dts/rk3288.dtsi
@@ -241,6 +241,11 @@
status = "disabled";
};
+ pmu_intmem at ff720000 {
+ compatible = "mmio-sram", "rockchip,rk3288-pmu-sram";
+ reg = <0xff720000 0x4000>;
+ };
+
pmu: power-management at ff730000 {
compatible = "rockchip,rk3288-pmu", "syscon";
reg = <0xff730000 0x100>;
@@ -421,6 +426,12 @@
bias-disable;
};
+ sleep {
+ global_pwroff: global-pwroff {
+ rockchip,pins = <0 0 RK_FUNC_1 &pcfg_pull_none>;
+ };
+ };
+
i2c0 {
i2c0_xfer: i2c0-xfer {
rockchip,pins = <0 15 RK_FUNC_1 &pcfg_pull_none>,
--
1.7.9.5
next prev parent reply other threads:[~2014-10-15 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 20:46 [PATCH 0/4] add suspend support for RK3288 zyw at rock-chips.com
2014-10-15 20:47 ` [PATCH 1/4] ARM: rockchip: add suspend and resume " zyw at rock-chips.com
2014-10-16 3:44 ` Doug Anderson
2014-10-15 20:48 ` [PATCH 2/4] clk: rockchip: RK3288: add suspend and resume zyw at rock-chips.com
2014-10-16 3:34 ` Doug Anderson
2014-10-15 20:49 ` zyw at rock-chips.com [this message]
2014-10-16 3:43 ` [PATCH 3/4] ARM: dts: add RK3288 suspend support Doug Anderson
2014-10-16 10:20 ` Mark Rutland
2014-10-15 20:50 ` [PATCH 4/4] ARM: rockchip: add pmu-sram sub zyw at rock-chips.com
2014-10-16 3:41 ` Doug Anderson
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=1413406144-16329-1-git-send-email-zyw@rock-chips.com \
--to=zyw@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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