From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
ming.m.lin@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, Zheng Yan <zheng.z.yan@intel.com>
Subject: Re: [RFC v2 1/5] PM, Runtime, Add power_must_be_on flag
Date: Mon, 7 May 2012 22:33:00 +0200 [thread overview]
Message-ID: <201205072233.01110.rjw@sisk.pl> (raw)
In-Reply-To: <CAC=cRTOpbbHCSXN3=JKZkpy753G0-Vgbu0DkbV-v_coVMM7Qzw@mail.gmail.com>
On Saturday, May 05, 2012, huang ying wrote:
> On Sat, May 5, 2012 at 3:37 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Friday, May 04, 2012, Huang Ying wrote:
> >> The extreme way to save device power in runtime is to turn off power
> >> of device. For example, D3cold for PCIe bus and ZPODD (Zero Power
> >> Optical Disk Drive) for SATA bus will do that.
> >>
> >> But sometimes power off is not expected, some possible reason is as
> >> follow
> >>
> >> - power off device usually incurs longer resume latency, if it exceeds
> >> power QoS requirement, power off should be disabled.
> >>
> >> - For some buses, device in power off state can not support remote
> >> wakeup. If remote wakeup is desired, power off should be disabled.
> >>
> >> In general, whether to put a device into power off state should be
> >> decided by the driver of the device, but for some buses, whether to
> >> put a device into power off state may be done by the parent of the
> >> device. For example, a PCIe end point device may be put into power
> >> off state by the PCIe port connected to it.
> >>
> >> So a flag is introduced for the children devices to tell the parent
> >> device, whether it should be put into power off state.
> >>
> >> This flag is also used for device driver to tell bus layer whether it
> >> is OK to be powered off.
> >>
> >> Signed-off-by: Huang Ying <ying.huang@intel.com>
> >
> > I would be almost fine with this patch, if [2/5] were not present.
> >
> > However, if you introduce a flag like this, you need to put checks
> > against it into all places where power may be removed from devices,
> > like the generic PM domains framework (but not only there).
>
> Yes. At least this flag will be needed by other buses, like ZPODD
> support from Lin Ming:
>
> https://lkml.org/lkml/2012/3/28/23
>
> So my original plan is to introduce this flag firstly, then to add
> checking for this flag in various places need it.
That sounds like a good plan, but then please don't export this to user
space as long as the kernel side is complete.
> Do you suggest to
> put PCIe D3cold support, ZPODD support, power domain related checking
> into one patchset.
This isn't necessary so long as the flag is not exported.
Thanks,
Rafael
next prev parent reply other threads:[~2012-05-07 20:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 8:13 [RFC v2 0/5] PCIe, Add PCIe runtime D3cold support Huang Ying
2012-05-04 8:13 ` [RFC v2 1/5] PM, Runtime, Add power_must_be_on flag Huang Ying
2012-05-04 19:37 ` Rafael J. Wysocki
2012-05-05 5:15 ` huang ying
2012-05-07 20:33 ` Rafael J. Wysocki [this message]
2012-05-04 19:50 ` Bjorn Helgaas
2012-05-05 5:59 ` huang ying
2012-05-07 20:37 ` Rafael J. Wysocki
2012-05-04 8:13 ` [RFC v2 2/5] PM, Add sysfs file power_off to control device power off policy Huang Ying
2012-05-04 19:33 ` Rafael J. Wysocki
2012-05-05 6:29 ` huang ying
2012-05-07 20:53 ` Rafael J. Wysocki
2012-05-08 1:44 ` Huang Ying
2012-05-08 21:34 ` Rafael J. Wysocki
2012-05-09 6:46 ` Huang Ying
2012-05-09 10:38 ` Rafael J. Wysocki
2012-05-10 0:55 ` Huang Ying
2012-05-10 14:48 ` Alan Stern
2012-05-10 19:03 ` Rafael J. Wysocki
2012-05-04 19:50 ` Bjorn Helgaas
2012-05-04 21:00 ` Rafael J. Wysocki
2012-05-05 6:36 ` huang ying
2012-05-04 8:13 ` [RFC v2 3/5] PCIe, Add runtime PM support to PCIe port Huang Ying
2012-05-04 19:43 ` Rafael J. Wysocki
2012-05-05 6:46 ` huang ying
2012-05-07 21:00 ` Rafael J. Wysocki
2012-05-11 7:57 ` Huang Ying
2012-05-11 18:44 ` Rafael J. Wysocki
2012-05-04 19:50 ` Bjorn Helgaas
2012-05-04 20:55 ` Rafael J. Wysocki
2012-05-05 6:54 ` huang ying
2012-05-07 21:06 ` Rafael J. Wysocki
2012-05-05 6:53 ` huang ying
2012-05-04 8:13 ` [RFC v2 4/5] ACPI, PM, Specify lowest allowed state for device sleep state Huang Ying
2012-05-04 20:10 ` Rafael J. Wysocki
2012-05-05 7:25 ` huang ying
2012-05-07 21:15 ` Rafael J. Wysocki
2012-05-08 1:49 ` Huang Ying
2012-05-04 8:13 ` [RFC v2 5/5] PCIe, Add PCIe runtime D3cold support Huang Ying
2012-05-04 19:51 ` Bjorn Helgaas
2012-05-05 7:34 ` huang ying
2012-05-04 20:50 ` Rafael J. Wysocki
2012-05-05 8:08 ` huang ying
2012-05-07 21:22 ` Rafael J. Wysocki
2012-05-08 2:22 ` Huang Ying
2012-05-08 8:34 ` Huang Ying
2012-05-10 19:28 ` Rafael J. Wysocki
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=201205072233.01110.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=ying.huang@intel.com \
--cc=zheng.z.yan@intel.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).