From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Lin 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 Message-ID: <562504B5.7090206@rock-chips.com> References: <1441961698-10516-1-git-send-email-shawn.lin@rock-chips.com> <56243E85.2040202@rock-chips.com> <5624AC51.9060907@rock-chips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org To: Ulf Hansson Cc: shawn.lin@rock-chips.com, Michal Simek , S?ren Brinkmann , linux-mmc , "linux-kernel@vger.kernel.org" , "open list:ARM/Rockchip SoC..." , "devicetree@vger.kernel.org" List-Id: devicetree@vger.kernel.org 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