From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Feng Hong <hongfeng@marvell.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Why rpm_idle called in rpm_resume ?
Date: Mon, 13 May 2013 13:55:31 +0200 [thread overview]
Message-ID: <4976623.KzG9Mg72uv@vostro.rjw.lan> (raw)
In-Reply-To: <E62404B31D39064FBDD0B843ADF05A7D2DF42CF662@SC-VEXCH4.marvell.com>
On Monday, May 13, 2013 12:18:31 AM Feng Hong wrote:
> Hi, All,
>
> Recently, I'm reviewing the runtime implementation, there is one logical puzzle me
> a lot, can you help to explain ?
That's because the resume may be spurious and in fact it may be possible to suspend
the device again, which we want to happen if so.
Thanks,
Rafael
> See below, if rpm_callback called with successful return in rpm_resume, rpm_idle will be called, what's the purpose on it ? The device just comeback to active, why call rpm_idle to try to suspend it ?
> static int rpm_resume(struct device *dev, int rpmflags)
> {
> ...
> retval = rpm_callback(callback, dev);
> if (retval) {
> ...
> } else {
> __update_runtime_status(dev, RPM_ACTIVE)
> ...
> }
> if (!retval)
> rpm_idle(dev, RPM_ASYNC);
> ....
> }
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-05-13 11:46 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:54 [PATCH 00/18] For-3.10: CPUFreq: Move drivers to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 01/18] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 02/18] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 03/18] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 04/18] cpufreq: pxa3xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 05/18] cpufreq: pxa2xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 06/18] cpufreq: integrator: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 7:06 ` Viresh Kumar
2013-04-05 7:06 ` Viresh Kumar
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:41 ` Kukjin Kim
2013-04-08 10:41 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 18:12 ` Rafael J. Wysocki
2013-04-25 18:12 ` Rafael J. Wysocki
2013-04-25 18:12 ` Rafael J. Wysocki
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 7:18 ` Why rpm_idle called in rpm_resume ? Feng Hong
2013-05-13 11:55 ` Rafael J. Wysocki [this message]
2013-05-13 10:51 ` [PATCH 07/18] cpufreq: s3c24xx: move cpufreq driver to drivers/cpufreq Rafael J. Wysocki
2013-05-13 10:51 ` Rafael J. Wysocki
2013-05-13 10:46 ` Viresh Kumar
2013-05-13 10:46 ` Viresh Kumar
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-20 5:29 ` Viresh Kumar
2013-05-20 5:29 ` Viresh Kumar
2013-05-20 13:47 ` Kukjin Kim
2013-05-20 13:47 ` Kukjin Kim
2013-04-08 4:54 ` Viresh Kumar
2013-04-08 4:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 08/18] cpufreq: sa11x0: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 09/18] cpufreq: AVR32: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 10/18] cpufreq: blackfin: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 11/18] cpufreq: cris: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 12/18] cpufreq: ia64: " Viresh Kumar
2013-04-04 12:59 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 13/18] cpufreq: mips: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 14/18] cpufreq: sh: " Viresh Kumar
2013-04-04 12:58 ` Viresh Kumar
2013-04-09 12:55 ` Simon Horman
2013-04-09 12:55 ` Simon Horman
2013-04-09 14:12 ` Viresh Kumar
2013-04-09 14:24 ` Viresh Kumar
2013-04-10 2:12 ` Simon Horman
2013-04-10 2:12 ` Simon Horman
2013-04-10 2:51 ` Viresh Kumar
2013-04-10 2:51 ` Viresh Kumar
2013-04-10 4:30 ` Simon Horman
2013-04-10 4:30 ` Simon Horman
2013-04-04 12:54 ` [PATCH 15/18] cpufreq: unicore2: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 16/18] cpufreq: sparc: " Viresh Kumar
2013-04-04 12:58 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 17/18] cpufreq: powerpc: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-05 6:46 ` Viresh Kumar
2013-04-05 6:46 ` Viresh Kumar
2013-04-09 8:35 ` Viresh Kumar
2013-04-09 8:35 ` Viresh Kumar
2013-04-22 6:49 ` Viresh Kumar
2013-04-22 6:49 ` Viresh Kumar
2013-05-13 6:04 ` Viresh Kumar
2013-05-13 6:04 ` Viresh Kumar
2013-05-20 4:40 ` Viresh Kumar
2013-05-20 4:40 ` Viresh Kumar
2013-05-31 10:50 ` Viresh Kumar
2013-05-31 10:50 ` Viresh Kumar
2013-06-07 5:18 ` Viresh Kumar
2013-06-07 5:18 ` Viresh Kumar
2013-06-07 11:58 ` Rafael J. Wysocki
2013-06-07 11:58 ` Rafael J. Wysocki
2013-04-04 12:54 ` [PATCH 18/18] cpufreq: powerpc/platforms/cell: " Viresh Kumar
2013-04-04 12:54 ` Viresh Kumar
2013-04-04 13:02 ` Arnd Bergmann
2013-04-04 13:02 ` Arnd Bergmann
2013-04-04 13:50 ` Viresh Kumar
2013-04-04 13:50 ` Viresh Kumar
2013-04-04 14:48 ` Arnd Bergmann
2013-04-04 14:48 ` Arnd Bergmann
2013-04-04 22:36 ` [PATCH 00/18] For-3.10: CPUFreq: Move drivers " Rafael J. Wysocki
2013-04-05 1:17 ` Viresh Kumar
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=4976623.KzG9Mg72uv@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=hongfeng@marvell.com \
--cc=linux-pm@vger.kernel.org \
/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.