From: Lin Ming <ming.m.lin@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jeff Garzik <jgarzik@pobox.com>,
James Bottomley <JBottomley@parallels.com>,
Tejun Heo <tj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 2/3] [SCSI]: runtime resume parent for child's system-resume
Date: Thu, 15 Dec 2011 02:31:52 +0800 [thread overview]
Message-ID: <1323887512.7655.3.camel@hp6530s> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1112141150520.1707-100000@iolanthe.rowland.org>
On Thu, 2011-12-15 at 00:51 +0800, Alan Stern wrote:
> On Wed, 14 Dec 2011, Lin Ming wrote:
>
> > On Wed, Dec 14, 2011 at 11:18 AM, Lin Ming <ming.m.lin@intel.com> wrote:
> > > [Patch description from Alan Stern]
> > >
> > > If a child device was runtime-suspended when a system suspend began,
> > > then there will be nothing to prevent its parent from
> > > runtime-suspending as soon as it is woken up during the system resume.
> > > Then when the time comes to resume the child, the resume will fail
> > > because the parent is already back at low power.
> > >
> > > On the other hand, there are some devices which should remain at low
> > > power across an entire suspend-resume cycle. �The details depend on the
> > > device and the platform.
> > >
> > > This suggests that the PM core is not the right place to solve the
> > > problem. �One possible solution is for the subsystem or device driver
> > > to call pm_runtime_get_sync(dev->parent) at the start of the
> > > system-resume procedure and pm_runtime_put_sync(dev->parent) at the
> > > end.
> > >
> > > Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> >
> > Hi Alan,
> >
> > May I add your SOB?
>
> You can add: Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> Did you test this? Does it do what you want?
Yes, I have tested this and it fixes the problem.
Thanks.
>
> Alan Stern
>
next prev parent reply other threads:[~2011-12-14 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 3:17 [PATCH 0/3] fixes for ata port runtime pm support Lin Ming
2011-12-14 3:17 ` [PATCH 1/3] [SCSI] sd: fix runtime status check in sd_shutdown Lin Ming
2011-12-14 10:58 ` Sergei Shtylyov
2011-12-14 13:24 ` Lin Ming
2011-12-14 16:49 ` Alan Stern
2011-12-14 18:34 ` Lin Ming
2011-12-14 3:18 ` [PATCH 2/3] [SCSI]: runtime resume parent for child's system-resume Lin Ming
2011-12-14 3:20 ` Lin Ming
2011-12-14 16:51 ` Alan Stern
2011-12-14 18:31 ` Lin Ming [this message]
2011-12-14 3:18 ` [PATCH 3/3] ata: update ata port's runtime status during system resume Lin Ming
2011-12-14 18:45 ` Lin Ming
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=1323887512.7655.3.camel@hp6530s \
--to=ming.m.lin@intel.com \
--cc=JBottomley@parallels.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
/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