All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH][RFC] mfd: intel-lpss: Avoid resuming runtime-suspended lpss unnecessarily
Date: Mon, 12 Sep 2016 23:41:23 +0800	[thread overview]
Message-ID: <20160912154123.GA1986@sharon> (raw)
In-Reply-To: <20160912151704.GH9789@dell>

Hi,
On Mon, Sep 12, 2016 at 04:17:04PM +0100, Lee Jones wrote:
> On Sun, 04 Sep 2016, Chen Yu wrote:
> 
> > We have report that the intel_lpss_prepare() takes too much time during
> > suspend, and this is because we first resume the devices from runtime
> > suspend by resume_lpss_device(), to make sure they are in proper state
> > before system suspend, which takes 100ms for each LPSS devices(PCI power
> > state from D3_cold to D0). And since resume_lpss_device() resumes the
> > devices synchronously, we might get huge latency if we have many
> > LPSS devices.
> > 
> > So first try is to use pm_request_resume() instead, to make the runtime
> > resume process asynchronously. Unfortunately the asynchronous runtime
> > resume relies on pm_wq, which is freezed at early stage. So we choose
> > another method, that is to avoid resuming runtime-suspended devices,
> > if they are already runtime suspended. This is safe because for LPSS
> > driver, the runtime suspend and system suspend are of the same
> > hook - i.e., intel_lpss_suspend(). And moreover, this device is
> > neither runtime wakeup source nor system wakeup source.
> > 
> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > Signed-off-by: Chen Yu <yu.c.chen@intel.com>
> > ---
> >  drivers/mfd/intel-lpss.c | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> > 
> > diff --git a/drivers/mfd/intel-lpss.c b/drivers/mfd/intel-lpss.c
> > index 41b1138..6dcc9a0 100644
> > --- a/drivers/mfd/intel-lpss.c
> > +++ b/drivers/mfd/intel-lpss.c
> > @@ -485,6 +485,15 @@ static int resume_lpss_device(struct device *dev, void *data)
> >  int intel_lpss_prepare(struct device *dev)
> >  {
> >  	/*
> > +	 * This is safe because:
> > +	 * 1. The runtime suspend and system suspend
> > +	 * are of the same hook.
> > +	 * 2. This device is neither runtime wakeup source
> > +	 * nor system wakeup source.
> > +	 */
> > +	if (pm_runtime_status_suspended(dev))
> > +		return 1;
> 
> What's '1'?
> 
According to the comment in device_prepare():

A positive return value from ->prepare() means "this device appears
to be runtime-suspended and its state is fine, so if it really is
runtime-suspended, you can leave it in that state provided that you
will do the same thing with all of its descendants". 

Thanks,
Yu

  reply	other threads:[~2016-09-12 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 15:58 [PATCH][RFC] mfd: intel-lpss: Avoid resuming runtime-suspended lpss unnecessarily Chen Yu
2016-09-12 15:17 ` Lee Jones
2016-09-12 15:41   ` Chen Yu [this message]
2016-09-13  8:24     ` Lee Jones
2016-09-13 12:15       ` Rafael J. Wysocki
2016-09-20  0:18         ` Chen, Yu C
2016-09-27 18:49           ` Lee Jones

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=20160912154123.GA1986@sharon \
    --to=yu.c.chen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@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 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.