linux-kernel - Re: [PATCH v2 0/3] pmdomain: ti_sci: collect and send low-power mode constraints

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: <20240820100713.2xbbyw726eymxr66@lcpd911>
Date: Tue, 20 Aug 2024 15:37:13 +0530
From: Dhruva Gole <d-gole@...com>
To: Kevin Hilman <khilman@...libre.com>
CC: Ulf Hansson <ulf.hansson@...aro.org>, <linux-pm@...r.kernel.org>,
        Nishanth
 Menon <nm@...com>, Vibhore Vardhan <vibhore@...com>,
        Akashdeep Kaur
	<a-kaur@...com>, Sebin Francis <sebin.francis@...com>,
        Markus
 Schneider-Pargmann <msp@...libre.com>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] pmdomain: ti_sci: collect and send low-power mode
 constraints

On Aug 19, 2024 at 17:00:10 -0700, Kevin Hilman wrote:
> The latest (10.x) version of the firmware for the PM co-processor (aka
> device manager, or DM) adds support for a "managed" mode, where the DM
> firmware will select the specific low power state which is entered
> when Linux requests a system-wide suspend.
> 
> In this mode, the DM will always attempt the deepest low-power state
> available for the SoC.
> 
> However, Linux (or OSes running on other cores) may want to constrain
> the DM for certain use cases.  For example, the deepest state may have
> a wakeup/resume latency that is too long for certain use cases.  Or,
> some wakeup-capable devices may potentially be powered off in deep
> low-power states, but if one of those devices is enabled as a wakeup
> source, it should not be powered off.
> 
> These kinds of constraints are are already known in Linux by the use
> of existing APIs such as per-device PM QoS and device wakeup APIs, but
> now we need to communicate these constraints to the DM.
> 
> For TI SoCs with TI SCI support, all DM-managed devices will be
> connected to a TI SCI PM domain.  So the goal of this series is to use
> the PM domain driver for TI SCI devices to collect constraints, and
> communicate them to the DM via the new TI SCI APIs.
> 
> This is all managed by TI SCI PM domain code.  No new APIs are needed
> by Linux drivers.  Any device that is managed by TI SCI will be
> checked for QoS constraints or wakeup capability and the constraints
> will be collected and sent to the DM.
> 
> This series depends on the support for the new TI SCI APIs (v10) and
> was also tested with this series to update 8250_omap serial support
> for AM62x[2].
> 
> [1] https://lore.kernel.org/all/20240801195422.2296347-1-msp@baylibre.com
> [2] https://lore.kernel.org/all/20240807141227.1093006-1-msp@baylibre.com/
> 
> Signed-off-by: Kevin Hilman <khilman@...libre.com>
> ---

Since I applied this series to the v10 TISCI series as well, and tested:

For the series,
Tested-by: Dhruva Gole <d-gole@...com>

Logs:
https://gist.github.com/DhruvaG2000/658d0d4683b13ab41025df19a8eafc2f

Tree with all the patches applied:
https://github.com/DhruvaG2000/v-linux/tree/lpm-k3-next

-- 
Best regards,
Dhruva Gole <d-gole@...com>