From: Johan Hovold <johan@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] PM / runtime: Drop children check from __pm_runtime_set_status()
Date: Thu, 16 Nov 2017 10:22:41 +0100 [thread overview]
Message-ID: <20171116092241.GI11226@localhost> (raw)
In-Reply-To: <1713438.irjm9MTSvo@aspire.rjw.lan>
On Sun, Nov 12, 2017 at 01:27:30AM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The check for "active" children in __pm_runtime_set_status(), when
> trying to set the parent device status to "suspended", doesn't
> really make sense, because in fact it is not invalid to set the
> status of a device with runtime PM disabled to "suspended" in any
> case. It is invalid to enable runtime PM for a device with its
> status set to "suspended" while its child_count reference counter
> is nonzero, but the check in __pm_runtime_set_status() doesn't
> really cover that situation.
>
> For this reason, drop the children check from __pm_runtime_set_status()
> and add a check against child_count reference counters of "suspended"
> devices to pm_runtime_enable().
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Looks good to me, but you should also fix
Documentation/power/runtime_pm.txt which was updated to reflect the
constraint that is now being reverted.
Reviewed-by: Johan Hovold <johan@kernel.org>
Thanks,
Johan
next prev parent reply other threads:[~2017-11-16 9:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 0:27 [PATCH] PM / runtime: Drop children check from __pm_runtime_set_status() Rafael J. Wysocki
2017-11-13 13:26 ` Ulf Hansson
2017-11-13 21:50 ` Rafael J. Wysocki
2017-11-13 21:58 ` Rafael J. Wysocki
2017-11-14 9:13 ` Ulf Hansson
2017-11-14 9:56 ` Ulf Hansson
2017-11-14 21:44 ` Rafael J. Wysocki
2017-11-15 7:22 ` Ulf Hansson
2017-11-16 9:22 ` Johan Hovold [this message]
2017-11-16 13:57 ` Rafael J. Wysocki
2017-11-28 10:58 ` Geert Uytterhoeven
2017-11-28 12:48 ` Yoshihiro Shimoda
2017-11-28 15:06 ` Alan Stern
2017-11-29 8:21 ` Yoshihiro Shimoda
2017-11-28 17:22 ` Ulf Hansson
2017-11-29 8:21 ` Yoshihiro Shimoda
2017-11-29 9:24 ` Ulf Hansson
2017-11-29 9:43 ` Geert Uytterhoeven
2017-11-29 9:59 ` Ulf Hansson
2017-11-29 14:09 ` Geert Uytterhoeven
2017-11-30 12:51 ` Yoshihiro Shimoda
2017-12-01 9:22 ` Ulf Hansson
2017-12-01 11:03 ` Yoshihiro Shimoda
2017-12-01 11:54 ` Yoshihiro Shimoda
2017-12-04 10:41 ` Ulf Hansson
[not found] ` <CAPDyKFr4=Vct_-w1euOsEnb3WdeBvH9mz12zNTUfX7Z6nEwRuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-05 3:23 ` Yoshihiro Shimoda
2017-12-05 15:03 ` Alan Stern
2017-12-05 15:23 ` Rafael J. Wysocki
2017-12-05 15:48 ` Ulf Hansson
2017-11-28 14:17 ` Rafael J. Wysocki
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=20171116092241.GI11226@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).