From: Heiko Stuebner <heiko@sntech.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Ziyuan Xu <xzy.xu@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
zhangqing <zhangqing@rock-chips.com>
Subject: Re: [PATCH v3 1/2] Documentation: mmc: sdhci-of-arasan: add description of power domain
Date: Sat, 17 Sep 2016 11:57:00 +0200 [thread overview]
Message-ID: <2176583.VnE4kDODlR@phil> (raw)
In-Reply-To: <CAPDyKFo6332LYwLk8xBz8aNQiLC+FEc5-1yY-jHPMm2ReXC=bQ@mail.gmail.com>
Am Samstag, 17. September 2016, 11:09:15 CEST schrieb Ulf Hansson:
> On 17 September 2016 at 11:01, Heiko Stuebner <heiko@sntech.de> wrote:
> > Hi,
> >
> > Am Samstag, 17. September 2016, 10:32:49 CEST schrieb Ziyuan Xu:
> >> Add power domain as a optional property for sdhci-of-arasan, which can
> >> be turned off in the so-called unused condition, such as suspend and
> >> remove. Aim to lower power requirements.
> >>
> >> Signed-off-by: Ziyuan Xu <xzy.xu@rock-chips.com>
> >>
> >> Acked-by: Rob Herring <robh@kernel.org>
> >
> > Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> >
> > @Ulf: I guess you'll take this binding change through the mmc tree and
> > I'll
> > pick up the devicetree change.
>
> Ideally the documentation and DT change should go together, so I think
> it's better for you to pick up both.
I was more thinking about future conflicts with possible other changes during
the 4.9 cycle. We have -rc7 now, so arm-soc is pretty off limits for new
changes thus the binding change would only land in time for 4.10 and may cause
conflicts then.
> I intend to ack it, although it would be nice with some more
> information as I requested, in the change-log first.
I guess we'll just wait until you are comfortable with the change and decide
then through which trees it should go :-)
Heiko
> >> ---
> >>
> >> Changes in v3:
> >> - fix a typo
> >> - add Rob's ack-tag
> >>
> >> Changes in v2:
> >> - fix a typo
> >> - add an example code for power-domain
> >>
> >> Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 7 ++++++-
> >> 1 file changed, 6 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
> >> b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt index
> >> 3404afa..eb84d29 100644
> >> --- a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
> >> +++ b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
> >> @@ -1,12 +1,14 @@
> >>
> >> Device Tree Bindings for the Arasan SDHCI Controller
> >>
> >> - The bindings follow the mmc[1], clock[2], interrupt[3] and phy[4]
> >> bindings. + The bindings follow the mmc[1], clock[2], interrupt[3],
> >> phy[4]
> >> and power + domain[5] bindings.
> >>
> >> Only deviations are documented here.
> >>
> >> [1] Documentation/devicetree/bindings/mmc/mmc.txt
> >> [2] Documentation/devicetree/bindings/clock/clock-bindings.txt
> >> [3]
> >> Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
> >>
> >> [4] Documentation/devicetree/bindings/phy/phy-bindings.txt
> >> + [5] Documentation/devicetree/bindings/power/power_domain.txt
> >>
> >> Required Properties:
> >> - compatible: Compatibility string. One of:
> >> @@ -36,6 +38,8 @@ Optional Properties:
> >> - #clock-cells: If specified this should be the value <0>. With this
> >>
> >> property in place we will export a clock representing the Card Clock.
> >> This
> >> clock is expected to be consumed by our PHY. You must also specify + -
> >> power-domains: A phandle and PM domain as specifier defined by bindings +
> >>
> >> of the power controller specified by phandle.
> >>
> >> Example:
> >> sdhci@e0100000 {
> >>
> >> @@ -71,5 +75,6 @@ Example:
> >> phys = <&emmc_phy>;
> >> phy-names = "phy_arasan";
> >> #clock-cells = <0>;
> >>
> >> + power-domains = <&power RK3399_PD_EMMC>;
> >>
> >> status = "disabled";
> >>
> >> };
next prev parent reply other threads:[~2016-09-17 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 2:32 [PATCH v3 0/2] Add power domain support for eMMC node on rk3399 Ziyuan Xu
[not found] ` <20160917023250.1159-1-xzy.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-09-17 2:32 ` [PATCH v3 1/2] Documentation: mmc: sdhci-of-arasan: add description of power domain Ziyuan Xu
2016-09-17 8:49 ` Ulf Hansson
[not found] ` <CAPDyKFrgdsppLg9RkCsSh4nhjUiJR6D4u+E8qnzfbtNxhwLOmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-20 2:29 ` Ziyuan Xu
2016-09-22 7:14 ` Ulf Hansson
[not found] ` <20160917023250.1159-2-xzy.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-09-17 9:01 ` Heiko Stuebner
2016-09-17 9:09 ` Ulf Hansson
2016-09-17 9:57 ` Heiko Stuebner [this message]
2016-09-17 2:32 ` [PATCH v3 2/2] arm64: dts: rockchip: add eMMC's power domain support for rk3399 Ziyuan Xu
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=2176583.VnE4kDODlR@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.org \
--cc=xzy.xu@rock-chips.com \
--cc=zhangqing@rock-chips.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).