From: Heiko Stuebner <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux-rockchip@lists.infradead.org, dbasehore@chromium.org,
robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will.deacon@arm.com,
briannorris@chromium.org, yamada.masahiro@socionext.com,
olof@lixom.net, jay.xu@rock-chips.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: add ap_pwroff and ddrio_pwroff pins for rk3399
Date: Mon, 27 Jun 2016 01:09:08 +0200 [thread overview]
Message-ID: <3506480.G5PcqxtUXs@phil> (raw)
In-Reply-To: <1465935671-13890-1-git-send-email-dianders@chromium.org>
Am Dienstag, 14. Juni 2016, 13:21:11 schrieb Douglas Anderson:
> There are two sleep related pins on rk3399: ap_pwroff and ddrio_pwroff.
> Let's add the definition of these two pins to rk3399's main dtsi file so
> that boards can use them.
>
> These two pins are similar to the global_pwroff and ddrio_pwroff pins in
> rk3288 and are expected to be used in the same way: boards will likely
> want to configure these pinctrl settings in their global pinctrl hog
> list.
>
> Note that on rk3288 there were two additional pins in the "sleep"
> section: "ddr0_retention" and "ddr1_retention". On rk3288 designs these
> pins appeared to actually route from rk3288 back to rk3288. Presumably
> on rk3399 this is simply not needed since the pins don't appear to exist
> there.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied to my dts64 branch for 4.8
Thanks
Heiko
prev parent reply other threads:[~2016-06-26 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 20:21 [PATCH] arm64: dts: rockchip: add ap_pwroff and ddrio_pwroff pins for rk3399 Douglas Anderson
2016-06-26 23:09 ` Heiko Stuebner [this message]
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=3506480.G5PcqxtUXs@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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).