mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: linux-kernel@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, lee.jones@linaro.org,
	rui.zhang@intel.com
Subject: [RFC] intel-lpss: remove .prepare() callback
Date: Thu, 25 Jan 2018 16:12:45 +0800	[thread overview]
Message-ID: <1516867965-11124-1-git-send-email-rui.zhang@intel.com> (raw)

The .prepare() callback of intel-lpss driver does nothing but wakes up its
children. I don't know if there is any reason to do so, but to me, this is
not preferred because it should be the child device driver to do so when
necessary, not the parent device driver.
Plus, .prepare() does not support asynchronization.

For example, on MS Surface Pro 4, there are 4 intel-lpss devices which
are runtime suspended before system suspend, resuming each of them takes
more than 100 milliseconds. Thus the .prepare() of intel-lpss driver takes
400ms+ on my surface pro 4, and I've seen platforms with 16 intel lpss
devices.

With this patch applied, the child devices are resumed in the .suspend()
stage of the child device, and they are done in parallel, thus only 100ms
is needed, no matter how many intel lpss devices there are.

I have tested it on three different platforms and didn't find any obvious
problem caused by this patch, and it indeed reduces the suspend time a lot.

Signed-off-by: Zhang Rui <rui.zhang@intel.com>
---
 drivers/mfd/intel-lpss.c | 11 -----------
 drivers/mfd/intel-lpss.h |  2 --
 2 files changed, 13 deletions(-)

diff --git a/drivers/mfd/intel-lpss.c b/drivers/mfd/intel-lpss.c
index 0e0ab9b..5ff31e9 100644
--- a/drivers/mfd/intel-lpss.c
+++ b/drivers/mfd/intel-lpss.c
@@ -482,17 +482,6 @@ static int resume_lpss_device(struct device *dev, void *data)
 	return 0;
 }
 
-int intel_lpss_prepare(struct device *dev)
-{
-	/*
-	 * Resume both child devices before entering system sleep. This
-	 * ensures that they are in proper state before they get suspended.
-	 */
-	device_for_each_child_reverse(dev, NULL, resume_lpss_device);
-	return 0;
-}
-EXPORT_SYMBOL_GPL(intel_lpss_prepare);
-
 int intel_lpss_suspend(struct device *dev)
 {
 	struct intel_lpss *lpss = dev_get_drvdata(dev);
diff --git a/drivers/mfd/intel-lpss.h b/drivers/mfd/intel-lpss.h
index 865bbea..7913b58 100644
--- a/drivers/mfd/intel-lpss.h
+++ b/drivers/mfd/intel-lpss.h
@@ -31,13 +31,11 @@ int intel_lpss_probe(struct device *dev,
 void intel_lpss_remove(struct device *dev);
 
 #ifdef CONFIG_PM
-int intel_lpss_prepare(struct device *dev);
 int intel_lpss_suspend(struct device *dev);
 int intel_lpss_resume(struct device *dev);
 
 #ifdef CONFIG_PM_SLEEP
 #define INTEL_LPSS_SLEEP_PM_OPS			\
-	.prepare = intel_lpss_prepare,		\
 	SET_LATE_SYSTEM_SLEEP_PM_OPS(intel_lpss_suspend, intel_lpss_resume)
 #else
 #define INTEL_LPSS_SLEEP_PM_OPS
-- 
2.7.4

             reply	other threads:[~2018-01-25  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  8:12 Zhang Rui [this message]
2018-01-25 12:28 ` Andy Shevchenko
2018-01-26 15:07   ` Zhang Rui

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=1516867965-11124-1-git-send-email-rui.zhang@intel.com \
    --to=rui.zhang@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 \
    /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

all inboxes | Powered by JetHome®