From: Kevin Hilman <khilman@baylibre.com>
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Akashdeep Kaur <a-kaur@ti.com>,
Markus Schneider-Pargmann <msp@baylibre.com>,
Vibhore Vardhan <vibhore@ti.com>, Dhruva Gole <d-gole@ti.com>
Subject: Re: [PATCH v3] firmware: ti_sci: add CPU latency constraint management
Date: Tue, 06 Aug 2024 09:01:19 -0700 [thread overview]
Message-ID: <7hwmkt1vzk.fsf@baylibre.com> (raw)
In-Reply-To: <20240806154415.wrsqxgyqdi2y4ae6@candy>
Nishanth Menon <nm@ti.com> writes:
> On 14:42-20240802, Kevin Hilman wrote:
>> 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@ti.com>
>> Signed-off-by: Vibhore Vardhan <vibhore@ti.com>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>> Signed-off-by: Dhruva Gole <d-gole@ti.com>
>> ---
>> Depends on the TI SCI series where support for the constraints APIs
>> are added:
>> https://lore.kernel.org/r/20240801195422.2296347-1-msp@baylibre.com
>>
>
> Unless there is a reason to maintain this patch separately, Could we
> add this to the mentioned series -> it is much easier to review and
> merge them in one go.
Sure, they can be combined for the next version.
Kevin
prev parent reply other threads:[~2024-08-06 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 21:42 [PATCH v3] firmware: ti_sci: add CPU latency constraint management Kevin Hilman
2024-08-06 15:44 ` Nishanth Menon
2024-08-06 16:01 ` Kevin Hilman [this message]
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=7hwmkt1vzk.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=a-kaur@ti.com \
--cc=d-gole@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=vibhore@ti.com \
/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).