[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4362123.MquenKSW7f@aspire.rjw.lan>
Date: Thu, 10 Aug 2017 00:11:54 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
LKML <linux-kernel@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Len Brown <lenb@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: [PATCH v2 0/4] PM: Replace "freeze" with "s2idle" in item names related to suspend-to-idle
On Saturday, August 5, 2017 2:55:34 PM CEST Rafael J. Wysocki wrote:
> Hi Everyone,
>
> The term "suspend-to-idle" (and its short form "s2idle") was invented after
> introducing support for the system state it refers to. At that time, the
> feature was called "freeze", kind of for the lack of a better idea how to
> call it.
>
> It would not be a problem if it wasn't confusing, but alas it is. The word
> "freeze" is quite heavily loaded in the PM terminology. It is related to
> the freezing of tasks, the freezing of filesystems (which isn't only used
> for PM for that matter), and one of the phases of handling devices during
> hibernation (and during resume from it) is called "freeze", which is reflected
> in the names of PM callbacks used by it.
>
> To avoid that confusion, the following patches change the names of various
> items related to suspend-to-idle by replacing the word "freeze" in them
> with "s2idle".
>
> The series is on top of current linux-next.
The v2 addresses the comment from Peter that PM_SUSPEND_S2IDLE had too many
"suspends" in it, so it is now replaced with PM_SUSPEND_TO_IDLE. No other
changes.
Thanks,
Rafael
Powered by blists - more mailing lists