From: Jisheng Zhang <jszhang@marvell.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Zhoujie Wu <zjwu@marvell.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Jimmy Xu <zmxu@marvell.com>, Nadav Haklai <nadavh@marvell.com>,
Victor Gu <xigu@marvell.com>, Wilson Ding <dingwei@marvell.com>,
Kostya Porotchkin <kostap@marvell.com>,
Hanna Hawa <hannah@marvell.com>,
hongd@marvell.com, Doug Jones <dougj@marvell.com>,
Ryan Gao <ygao@marvell.com>, "Wei(SOCP) Liu" <liuw@marvell.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH v3] mmc: sdhci-xenon: Add Xenon SDHCI specific system-level PM support
Date: Thu, 13 Jul 2017 17:25:59 +0800 [thread overview]
Message-ID: <20170713172559.6dd2d65a@xhacker> (raw)
In-Reply-To: <CAPDyKFpOcDOi8+nPsw0dk_rhcvzP94C9Mmp+RX=hfLvNqEs6sg@mail.gmail.com>
Hi Ulf,
On Thu, 13 Jul 2017 11:18:32 +0200 Ulf Hansson wrote:
> On 13 July 2017 at 00:16, Zhoujie Wu <zjwu@marvell.com> wrote:
> > From: Hu Ziji <huziji@marvell.com>
> >
> > Add Xenon specific system-level suspend and resume support.
> > Especially during resume, re-configure Xenon specific registers
> > since registers setting will be lost in suspend if Xenon is power off.
>
> I recommend to start with deploying runtime PM support instead of
> system PM support. Then on top of such change, you should make use of
> the runtime PM centric path to get system sleep support for "free"
> (and thus all the nice benefits).
I'm not sure whether runtime PM is useful for xenon case. The xenon HW
support ACG(Auto Clock Gating) and SDCLK-Off-While-Idle features, that's
to say we even don't need to do anything but achieve the runtime PM gains.
Thanks,
Jisheng
>
> Please have a look at sdhci-of-at91 for a good reference.
> Regarding sdhci-of-at91, there is currently a patch [1], which adds
> dealing with restoring context of registers after a system resume.
> Similar to what you need.
>
> Kind regards
> Uffe
>
> [1]
> https://patchwork.kernel.org/patch/9837951/
>
> [...]
>
> Kind regards
> Uffe
next prev parent reply other threads:[~2017-07-13 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 22:16 [PATCH v3] mmc: sdhci-xenon: Add Xenon SDHCI specific system-level PM support Zhoujie Wu
2017-07-13 9:18 ` Ulf Hansson
2017-07-13 9:25 ` Jisheng Zhang [this message]
2017-07-13 9:52 ` Ulf Hansson
2017-07-13 10:13 ` [EXT] " Jisheng Zhang
2017-07-13 10:48 ` Ulf Hansson
2017-07-13 11:03 ` Ulf Hansson
2017-07-13 21:45 ` Zhoujie Wu
2017-07-14 9:09 ` Ulf Hansson
2017-07-14 10:25 ` Ziji Hu
2017-08-07 9:18 ` Ulf Hansson
2017-07-14 18:46 ` Zhoujie Wu
2017-08-07 9:23 ` Ulf Hansson
2017-08-07 22:09 ` Zhoujie Wu
2017-08-14 11:11 ` Adrian Hunter
2017-08-21 12:33 ` Ulf Hansson
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=20170713172559.6dd2d65a@xhacker \
--to=jszhang@marvell.com \
--cc=adrian.hunter@intel.com \
--cc=dingwei@marvell.com \
--cc=dougj@marvell.com \
--cc=gregory.clement@free-electrons.com \
--cc=hannah@marvell.com \
--cc=hongd@marvell.com \
--cc=kostap@marvell.com \
--cc=linux-mmc@vger.kernel.org \
--cc=liuw@marvell.com \
--cc=nadavh@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ulf.hansson@linaro.org \
--cc=xigu@marvell.com \
--cc=ygao@marvell.com \
--cc=zjwu@marvell.com \
--cc=zmxu@marvell.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