From: Leo Li <pku.leo@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"Dongsheng Wang" <dongsheng.wang@freescale.com>,
"正雄 金" <jason.jin@freescale.com>,
"Zhao Chenhui" <chenhui.zhao@freescale.com>
Subject: Re: [PATCH v2 1/2] powerpc/pm: add api to get suspend state which is STANDBY or MEM
Date: Mon, 28 Apr 2014 13:53:06 +0800 [thread overview]
Message-ID: <CADRPPNTGRyLSSjcdpdZL95NVnRepR_ZqvVk1zrMU3ZOL0_bbNQ@mail.gmail.com> (raw)
In-Reply-To: <1398462328.24575.20.camel@snotra.buserror.net>
On Sat, Apr 26, 2014 at 5:45 AM, Scott Wood <scottwood@freescale.com> wrote:
> On Thu, 2014-04-24 at 14:11 +0800, Dongsheng Wang wrote:
>> From: Wang Dongsheng <dongsheng.wang@freescale.com>
>>
>> Add set_pm_suspend_state & pm_suspend_state functions to set/get
>> suspend state. When system going to sleep or deep sleep, devices
>> can get the system suspend state(STANDBY/MEM) through pm_suspend_state
>> function and to handle different situations.
>>
>> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
>> ---
>> *v2*
>> Move pm api from fsl platform to powerpc general framework.
>
> What is powerpc-specific about this?
Generally I agree with you. But I had the discussion about this topic
a while ago with the PM maintainer. He suggestion to go with the
platform way.
https://lkml.org/lkml/2013/8/16/505
Regards,
Leo
next prev parent reply other threads:[~2014-04-28 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 6:11 [PATCH v2 1/2] powerpc/pm: add api to get suspend state which is STANDBY or MEM Dongsheng Wang
2014-04-25 21:45 ` Scott Wood
2014-04-28 5:53 ` Leo Li [this message]
2014-04-29 22:47 ` Scott Wood
2014-04-29 23:07 ` Rafael J. Wysocki
2014-05-09 9:33 ` Li Yang
2014-05-09 17:09 ` Scott Wood
2014-05-10 12:35 ` Li Yang
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=CADRPPNTGRyLSSjcdpdZL95NVnRepR_ZqvVk1zrMU3ZOL0_bbNQ@mail.gmail.com \
--to=pku.leo@gmail.com \
--cc=chenhui.zhao@freescale.com \
--cc=dongsheng.wang@freescale.com \
--cc=jason.jin@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).