devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com, Michal Simek <michal.simek@xilinx.com>,
	S?ren Brinkmann <soren.brinkmann@xilinx.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan
Date: Mon, 19 Oct 2015 22:56:53 +0800	[thread overview]
Message-ID: <562504B5.7090206@rock-chips.com> (raw)
In-Reply-To: <CAPDyKFqyXNUS2GwPjVWpoiPxOLNJ3T=FgDLO2NT+pEBGYMR1eQ@mail.gmail.com>

On 2015/10/19 18:54, Ulf Hansson wrote:
> [...]
>

[...]

>
>>
>>> 2) Considering the runtime PM case for the sdhci device. Typically you
>>> can gate clocks etc at runtime suspend to save power, but what about
>>> the phy? Can you power off it in runtime suspend?
>>
>>
>> yes, we can power off it in runtime suspend. So we can append some patches
>> later to introduce runtime pm for sdhci-of-arasan?
>
> Yes, that's fine. I would thus expect that you want to do phy power
> off/on from the runtime PM callbacks, right!?
>
> If that's the case I think $subject patch should deal with *both* phy
> init and phy power on during ->probe().
>

yes. I will do phy power_off/on from runtime pm for the next version of 
$subject patchset.

Thanks.

> Kind regards
> Uffe
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>


-- 
Best Regards
Shawn Lin


      reply	other threads:[~2015-10-19 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  8:54 [PATCH 1/2] mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan Shawn Lin
2015-09-11  8:55 ` [PATCH 2/2] Documentation: bindings: add description of phy " Shawn Lin
     [not found]   ` <1441961729-10594-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-09-14  2:47     ` Sören Brinkmann
2015-09-14  3:02       ` Shawn Lin
2015-10-16 12:35 ` [PATCH 1/2] mmc: sdhci-of-arasan: add phy support " Ulf Hansson
     [not found]   ` <CAPDyKFpwgZSkE+TNehZ1Un=5CfjoEtfvELfrS6t-ZHZPscy3Yg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-19  0:51     ` Shawn Lin
     [not found]       ` <56243E85.2040202-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-10-19  7:50         ` Ulf Hansson
2015-10-19  8:39           ` Shawn Lin
     [not found]             ` <5624AC51.9060907-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-10-19 10:54               ` Ulf Hansson
2015-10-19 14:56                 ` Shawn Lin [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=562504B5.7090206@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).