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

On Thu, 2018-01-25 at 16:12 +0800, Zhang Rui wrote:
> 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.

> @@ -482,17 +482,6 @@ static int resume_lpss_device(struct device *dev,
> -	device_for_each_child_reverse(dev, NULL, resume_lpss_device);

Besides introduced compiler warning, did you check the latest linux-pm
changes? 

commit 8425ec7faff005500aad89b9fc00e5ba91ac57b9
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Jan 3 01:34:53 2018 +0100

    PM / mfd: intel-lpss: Use DPM_FLAG_SMART_SUSPEND


-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  8:12 Zhang Rui
2018-01-25 12:28 ` Andy Shevchenko [this message]
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=1516883334.7000.1252.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rui.zhang@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®