linux-kernel - Re: [PATCH] firmware: ti_sci: add CPU latency constraint management

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 for Android: free password hash cracker in your pocket

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

Message-ID: <7hed7662cv.fsf@baylibre.com>
Date: Fri, 02 Aug 2024 14:28:48 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>, Santosh
 Shilimkar <ssantosh@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 Akashdeep Kaur <a-kaur@...com>, Markus Schneider-Pargmann
 <msp@...libre.com>, Vibhore Vardhan <vibhore@...com>, Dhruva Gole
 <d-gole@...com>
Subject: Re: [PATCH] firmware: ti_sci: add CPU latency constraint management

Kevin Hilman <khilman@...libre.com> writes:

> During system-wide suspend, check if any of the CPUs have PM QoS
> resume latency constraints set.  If so, set TI SCI constraint.
>
> TI SCI has a single system-wide latency constraint, so use the max of
> any of the CPU latencies as the system-wide value.
>
> Note: DM firmware clears all constraints at resume time, so
> constraints need to be checked/updated/sent at each system suspend.
>
> Co-developed-by: Vibhore Vardhan <vibhore@...com>
> Signed-off-by: Vibhore Vardhan <vibhore@...com>
> Signed-off-by: Kevin Hilman <khilman@...libre.com>
> Reviewed-by: Dhruva Gole <d-gole@...com>
> Signed-off-by: Dhruva Gole <d-gole@...com>
> ---

Oops, please ignore.  A last minute "cleanup" caused this not to
compile. Sorry for the noise.  :(