From: Aaron Lu <aaron.lu@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jens Axboe <axboe@kernel.dk>, "Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-pm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>, Shane Huang <shane.huang@amd.com>
Subject: Re: [PATCH v9 4/4] sd: change to auto suspend mode
Date: Wed, 06 Feb 2013 10:10:41 +0800 [thread overview]
Message-ID: <5111BBA1.4010200@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1302051147370.2245-100000@iolanthe.rowland.org>
On 02/06/2013 12:51 AM, Alan Stern wrote:
> On Tue, 5 Feb 2013, Aaron Lu wrote:
>
>> From: Lin Ming <ming.m.lin@intel.com>
>>
>> Uses block layer runtime pm helper functions in
>> scsi_runtime_suspend/resume for devices that take advantage of it.
>>
>> Remove scsi_autopm_* from sd open/release path and check_events path.
>
> One thing is a little odd here...
>
>> --- a/drivers/scsi/scsi_pm.c
>> +++ b/drivers/scsi/scsi_pm.c
>> @@ -144,33 +144,78 @@ static int scsi_bus_restore(struct device *dev)
>>
>> #ifdef CONFIG_PM_RUNTIME
>>
>> +static int sdev_blk_runtime_suspend(struct scsi_device *sdev,
>> + int (*cb)(struct device *))
>> +{
>> + int err;
>> +
>> + err = blk_pre_runtime_suspend(sdev->request_queue);
>> + if (err)
>> + return err;
>> + if (cb)
>> + err = cb(&sdev->sdev_gendev);
>> + blk_post_runtime_suspend(sdev->request_queue, err);
>> +
>> + return err;
>> +}
>> +
>> +static int sdev_runtime_suspend(struct device *dev)
>> +{
>> + const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm : NULL;
>> + int (*cb)(struct device *) = pm ? pm->runtime_suspend : NULL;
>> + struct scsi_device *sdev = to_scsi_device(dev);
>> +
>> + if (sdev->request_queue->dev)
>> + return sdev_blk_runtime_suspend(sdev, cb);
>> + else
>> + return scsi_dev_type_suspend(dev, cb);
>> +}
>> +
>> static int scsi_runtime_suspend(struct device *dev)
>> {
>> int err = 0;
>> - const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm : NULL;
>>
>> dev_dbg(dev, "scsi_runtime_suspend\n");
>> - if (scsi_is_sdev_device(dev)) {
>> - err = scsi_dev_type_suspend(dev,
>> - pm ? pm->runtime_suspend : NULL);
>> - if (err == -EAGAIN)
>> - pm_schedule_suspend(dev, jiffies_to_msecs(
>> - round_jiffies_up_relative(HZ/10)));
>> - }
>> + if (scsi_is_sdev_device(dev))
>> + err = sdev_runtime_suspend(dev);
>
> The "if (err == -EAGAIN)" test and the call to pm_schedule_suspend seem
> to have been dropped since v8 of this series. It looks like they ought
> to be moved into sdev_runtime_suspend.
I thought they were no longer needed...
For sd, we have request based rutime PM and the PM core will always try
to autosuspend the device with the timer; and for sr, the poll will
trigger suspend constantly. And for both, we don't return -EAGAIN anyway.
So I suppose that code is not necessary?
BTW, I'll be on vocation till 02/17, and I don't have access to the
internet in my hometown, but please feel free to drop any comments and
I'll check them when I get back.
Thanks,
Aaron
next prev parent reply other threads:[~2013-02-06 2:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 8:03 [PATCH v9 0/4] block layer runtime pm Aaron Lu
2013-02-05 8:03 ` [PATCH v9 1/4] block: add a flag to identify PM request Aaron Lu
2013-02-05 8:03 ` [PATCH v9 2/4] block: add runtime pm helpers Aaron Lu
2013-02-05 8:03 ` [PATCH v9 3/4] block: implement runtime pm strategy Aaron Lu
2013-02-19 2:29 ` Aaron Lu
2013-02-19 16:34 ` Alan Stern
2013-02-05 8:03 ` [PATCH v9 4/4] sd: change to auto suspend mode Aaron Lu
2013-02-05 16:51 ` Alan Stern
2013-02-06 2:10 ` Aaron Lu [this message]
2013-02-06 15:51 ` Alan Stern
2013-02-18 3:20 ` Aaron Lu
2013-02-18 21:55 ` Alan Stern
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=5111BBA1.4010200@intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aaron.lwe@gmail.com \
--cc=axboe@kernel.dk \
--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=rjw@sisk.pl \
--cc=shane.huang@amd.com \
--cc=stern@rowland.harvard.edu \
/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).