From: Greg KH <gregkh@linuxfoundation.org>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: xf@rock-chips.com, heiko@sntech.de, rjw@rjwysocki.net,
khilman@kernel.org, ulf.hansson@linaro.org, pavel@ucw.cz,
len.brown@intel.com, linux-pm@vger.kernel.org,
huangtao@rock-chips.com, xxx@rock-chips.com, wxt@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM / Domains: Keep the pd status during system PM phases
Date: Fri, 20 Jan 2017 09:38:46 +0100 [thread overview]
Message-ID: <20170120083846.GB29509@kroah.com> (raw)
In-Reply-To: <1484878893-25270-1-git-send-email-zhangqing@rock-chips.com>
On Fri, Jan 20, 2017 at 10:21:33AM +0800, Elaine Zhang wrote:
> If a PM domain is powered off before system suspend,
> we hope do nothing in system runtime suspend noirq phase
> and system runtime resume noirq phase.
>
> This modify is to slove system resume issue for RK3399.
> RK3399 SOC pd_gpu have voltage domain vdd_gpu,
> so we must follow open vdd_gpu and power on pd_gpu,
> power off pd_gpu and disable vdd_gpu.
> Fix up in runtime resume noirq phase power on all PDs.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> drivers/base/power/domain.c | 10 +++++++---
> include/linux/pm_domain.h | 1 +
> 2 files changed, 8 insertions(+), 3 deletions(-)
What changed from v1? You always have to list that below the --- line.
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-20 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 2:21 [PATCH v2] PM / Domains: Keep the pd status during system PM phases Elaine Zhang
2017-01-20 8:38 ` Greg KH [this message]
2017-01-20 13:16 ` Ulf Hansson
2017-01-22 3:34 ` Elaine Zhang
2017-01-25 21:30 ` Ulf Hansson
2017-02-05 9:34 ` Elaine Zhang
2017-02-06 12:46 ` Ulf Hansson
2017-02-07 1:41 ` Elaine Zhang
2017-02-07 8:19 ` Ulf Hansson
2017-02-07 9:22 ` Elaine Zhang
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=20170120083846.GB29509@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.org \
--cc=wxt@rock-chips.com \
--cc=xf@rock-chips.com \
--cc=xxx@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).