All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Kendall Willis <k-willis@ti.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-pm@vger.kernel.org
Cc: Dhruva Gole <d-gole@ti.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] pmdommain: add support system-wide resume latency constraints
Date: Thu, 26 Feb 2026 09:43:01 -0800	[thread overview]
Message-ID: <7h342nqu3e.fsf@baylibre.com> (raw)
In-Reply-To: <057547c9-773e-4ba2-a754-aede29d07daa@ti.com>

Kendall Willis <k-willis@ti.com> writes:

> Hi Kevin,
> On 2/5/26 18:29, Kevin Hilman (TI) wrote:
>> In addition to checking for CPU latency constraints when checking if
>> OK to power down a domain, also check for QoS latency constraints in
>> all devices of a domain and use that in determining the final latency
>> constraint to use for the domain.
>> 
>> Since cpu_system_power_down_ok() is used for system-wide suspend, the
>> per-device constratints are only relevant if the LATENCY_SYS QoS flag
>> is set.
>> 
>> Signed-off-by: Kevin Hilman (TI) <khilman@baylibre.com>
>> ---
>
> Were you planning to also check the CPU devices QoS latency constraints 
> in the cpu_system_power_down_ok function? At present, this patch does 
> not add that functionality so if the PM_QOS_FLAG_LATENCY_SYS is present 
> for a CPU device, the QoS latency is not taken into account.

I did not add that functionality because the CPUs are managed by the new
system-wide /dev/cpu_wakeup_latency, which is already checked.

Kevin

  reply	other threads:[~2026-02-26 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  0:29 [PATCH v2 0/3] PM: QoS/pmdomains: support resume latencies for system-wide PM Kevin Hilman (TI)
2026-02-06  0:29 ` [PATCH v2 1/3] PM / QoS: add flag to indicate latency applies system-wide Kevin Hilman (TI)
2026-02-10 16:57   ` Rafael J. Wysocki
2026-02-06  0:29 ` [PATCH v2 2/3] pmdomain: core: add genpd_for_each_child() helper Kevin Hilman (TI)
2026-03-10 10:09   ` Ulf Hansson
2026-02-06  0:29 ` [PATCH v2 3/3] pmdommain: add support system-wide resume latency constraints Kevin Hilman (TI)
2026-02-11 21:29   ` Kendall Willis
2026-02-26 17:43     ` Kevin Hilman [this message]
2026-03-10 10:23   ` Ulf Hansson
2026-06-11 19:33     ` Kevin Hilman

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=7h342nqu3e.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=d-gole@ti.com \
    --cc=k-willis@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.