From: Tejun Heo <tj@kernel.org>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
lkml <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>,
Jeff Garzik <jgarzik@pobox.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <JBottomley@parallels.com>,
"Huang, Ying" <ying.huang@intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH v2 4/4] ata: add ata port runtime PM callbacks
Date: Tue, 15 Nov 2011 06:54:25 -0800 [thread overview]
Message-ID: <20111115145425.GL30922@google.com> (raw)
In-Reply-To: <1321347089.26084.2.camel@minggr>
On Tue, Nov 15, 2011 at 04:51:29PM +0800, Lin Ming wrote:
> > This is not the right approach. You should look instead at
> > scsi_dev_type_suspend() in scsi_pm.c. If the device is already runtime
> > suspended then the routine should return immediately.
>
> How about below?
>
> diff --git a/drivers/scsi/scsi_pm.c b/drivers/scsi/scsi_pm.c
> index d329f8b..94b60bd 100644
> --- a/drivers/scsi/scsi_pm.c
> +++ b/drivers/scsi/scsi_pm.c
> @@ -20,6 +20,9 @@ static int scsi_dev_type_suspend(struct device *dev, pm_message_t msg)
> struct device_driver *drv;
> int err;
>
> + if (pm_runtime_suspended(dev))
> + return 0;
> +
Something to be careful about is there are different types of suspend
states (PMSG_*). IIUC, runtime PM is using PMSG_SUSPEND. Other
states may or may not be compatible with PMSG_SUSPEND expectations, so
you can skip suspend operation if the newly requested state is
PMSG_SUSPEND but otherwise the controller needs to be woken up and
told to comply to the new state.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-11-15 14:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 6:22 [PATCH v2 0/4] ata port runtime power management support Lin Ming
2011-11-10 6:22 ` [PATCH v2 1/4] ata: make ata port as parent device of scsi host Lin Ming
2011-11-10 6:22 ` [PATCH v2 2/4] scsi: add flag to skip the runtime PM calls on host in EH Lin Ming
2011-11-10 6:22 ` [PATCH v2 3/4] ata: add ata port system PM callbacks Lin Ming
2011-11-10 6:22 ` [PATCH v2 4/4] ata: add ata port runtime " Lin Ming
2011-11-10 15:40 ` Alan Stern
2011-11-10 15:45 ` Tejun Heo
[not found] ` <CAF1ivSZ3rnb90u6LHXfWCBW-6mtfmWYjj1xXfABmm=uNVbomRw@mail.gmail.com>
2011-11-14 5:14 ` Lin Ming
2011-11-14 15:31 ` Alan Stern
2011-11-15 8:51 ` Lin Ming
2011-11-15 14:54 ` Tejun Heo [this message]
2011-11-15 16:08 ` Alan Stern
2011-11-16 13:14 ` Lin Ming
2011-11-16 15:42 ` Alan Stern
2011-11-10 15:30 ` [PATCH v2 0/4] ata port runtime power management support Tejun Heo
2011-11-10 15:31 ` Tejun Heo
2011-11-11 2:25 ` Lin Ming
2011-11-10 16:02 ` Kay Sievers
2011-11-11 2:33 ` Lin Ming
2011-11-10 15:30 ` Alan Stern
2011-11-10 15:37 ` Tejun Heo
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=20111115145425.GL30922@google.com \
--to=tj@kernel.org \
--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=ming.m.lin@intel.com \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=ying.huang@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).