linux-kernel - RE: [PATCH] PM: sleep: Add helpers to allow a device to remain powered-on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DU0PR04MB94175C3C8869A61403975E76881AA@DU0PR04MB9417.eurprd04.prod.outlook.com>
Date:   Thu, 17 Aug 2023 09:40:21 +0000
From:   Peng Fan <peng.fan@....com>
To:     Ulf Hansson <ulf.hansson@...aro.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
CC:     "Rafael J . Wysocki" <rjw@...ysocki.net>,
        Tony Lindgren <tony@...mide.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Patrice Chotard <patrice.chotard@...com>,
        Ajay Agarwal <ajayagarwal@...gle.com>,
        Michael Shavit <mshavit@...gle.com>,
        Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] PM: sleep: Add helpers to allow a device to remain
 powered-on

> Subject: [PATCH] PM: sleep: Add helpers to allow a device to remain
> powered-on
> 
> On some platforms a device and its corresponding PM domain, may need to
> remain powered-on during system wide suspend, to support various use
> cases.
> For example, when the console_suspend_enabled flag is unset for a serial
> controller, the corresponding device may need to remain powered on.
> Other use cases exists too.
> 
> In fact, we already have the mechanism in the PM core to deal with these
> kind of use cases. However, the current naming of the corresponding
> functions/flags clearly suggests these should be use for system wakeup.
> See device_wakeup_path(), device_set_wakeup_path and
> dev->power.wakeup_path.
> 
> As a way to extend the use of the existing mechanism, let's introduce two
> new helpers functions, device_awake_path() and device_set_awake_path().
> At this point, let them act as wrappers of the existing functions. Ideally,
> when all users have been converted to use the new helpers, we may decide
> to drop the old ones and rename the flag.
> 
> Signed-off-by: Ulf Hansson <ulf.hansson@...aro.org>

Reviewed-by: Peng Fan <peng.fan@....com>