From: Aaron Lu <aaron.lu@amd.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Alan Stern <stern@rowland.harvard.edu>,
Lin Ming <minggr@gmail.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH 4/5] scsi: pm: use runtime resume callback if available
Date: Tue, 24 Jul 2012 07:30:45 +0800 [thread overview]
Message-ID: <20120723233043.GA1965@localhost.localdomain> (raw)
In-Reply-To: <500D615C.1080605@mvista.com>
Hi,
On Mon, Jul 23, 2012 at 06:36:12PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 07/23/2012 10:49 AM, Aaron Lu wrote:
>
> > When runtime resume a scsi device, if the device's driver has
> > implemented runtime resume callback, use that instead of the resume
> > callback.
>
> > sr driver needs this to properly do different things for system resume
> > and runtime resume.
>
> > Signed-off-by: Aaron Lu <aaron.lu@amd.com>
> > ---
> > drivers/scsi/scsi_pm.c | 14 +++++++++-----
> > drivers/scsi/sr.c | 21 +++++++++++++++++++++
> > 2 files changed, 30 insertions(+), 5 deletions(-)
>
> > diff --git a/drivers/scsi/scsi_pm.c b/drivers/scsi/scsi_pm.c
> > index d4201de..19bba47 100644
> > --- a/drivers/scsi/scsi_pm.c
> > +++ b/drivers/scsi/scsi_pm.c
> > @@ -34,14 +34,18 @@ static int scsi_dev_type_suspend(struct device *dev, pm_message_t msg)
> > return err;
> > }
> >
> > -static int scsi_dev_type_resume(struct device *dev)
> > +static int scsi_dev_type_resume(struct device *dev, bool runtime)
> > {
> > struct device_driver *drv;
> > int err = 0;
> > + int (*resume)(struct device *);
> >
> > drv = dev->driver;
> > - if (drv && drv->resume)
> > - err = drv->resume(dev);
> > + if (runtime && drv && drv->pm && drv->pm->runtime_resume)
> > + resume = drv->pm->runtime_resume;
> > + else
> > + resume = drv ? drv->resume : NULL;
>
> Call thru NULL pointer below will cause kernel oops. Is it your intention?
Oops, I forgot the if check here, thanks for pointing this out.
-Aaron
>
> > + err = resume(dev);
>
next prev parent reply other threads:[~2012-07-23 23:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 6:49 [PATCH 0/5] Fix for ZPODD Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 6:49 ` [PATCH 1/5] scsi: sr: fix for sr suspend and resume Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 14:50 ` Alan Stern
2012-07-23 14:50 ` Alan Stern
2012-07-23 6:49 ` [PATCH 2/5] scsi: sr: runtime pm when ODD is open/closed Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 14:57 ` Alan Stern
2012-07-23 14:57 ` Alan Stern
2012-07-23 6:49 ` [PATCH 3/5] scsi: sr: block events when runtime suspended Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 6:49 ` [PATCH 4/5] scsi: pm: use runtime resume callback if available Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 14:36 ` Sergei Shtylyov
2012-07-23 23:30 ` Aaron Lu [this message]
2012-07-23 6:49 ` [PATCH 5/5] block: genhd: add an interface to set disk's poll interval Aaron Lu
2012-07-23 6:49 ` Aaron Lu
2012-07-23 18:43 ` Betty Dall
2012-07-23 23:52 ` Aaron Lu
2012-07-24 18:55 ` Betty Dall
2012-07-25 2:47 ` Aaron Lu
2012-07-25 2:47 ` Aaron Lu
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=20120723233043.GA1965@localhost.localdomain \
--to=aaron.lu@amd.com \
--cc=aaron.lwe@gmail.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=minggr@gmail.com \
--cc=sshtylyov@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.