Linux Power Management development
 help / color / mirror / Atom feed
From: Kendall Willis <k-willis@ti.com>
To: "Kevin Hilman (TI)" <khilman@baylibre.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	<linux-pm@vger.kernel.org>, "Ulf Hansson" <ulfh@kernel.org>,
	Dhruva Gole <d-gole@ti.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] PM / QoS: add flag to indicate latency applies system-wide
Date: Tue, 30 Jun 2026 16:11:12 -0500	[thread overview]
Message-ID: <20260630211112.eqagovk2y5uhdbkw@uda0506412> (raw)
In-Reply-To: <20260611-topic-lpm-pmdomain-device-constraints-v3-1-75d69438518b@baylibre.com>

On 12:59-20260611, Kevin Hilman (TI) wrote:
> By default, the QoS resume latency currenly only applied to runtime PM
> decisions.
> 
> Add new PM_QOS_FLAG_LATENCY_SYS flag to indicate that the
> resume latency QoS constraint should be applied to system-wide
> PM *in addition to* runtime PM.
> 
> Acked-by: Rafael J. Wysocki (Intel) <rafael@kernel.org>
> Signed-off-by: Kevin Hilman (TI) <khilman@baylibre.com>

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

> ---
>  include/linux/pm_qos.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/linux/pm_qos.h b/include/linux/pm_qos.h
> index 6cea4455f867..aededda52b6b 100644
> --- a/include/linux/pm_qos.h
> +++ b/include/linux/pm_qos.h
> @@ -37,6 +37,8 @@ enum pm_qos_flags_status {
>  #define PM_QOS_LATENCY_TOLERANCE_NO_CONSTRAINT	(-1)
>  
>  #define PM_QOS_FLAG_NO_POWER_OFF	(1 << 0)
> +/* latency value applies to system-wide suspend/s2idle */
> +#define PM_QOS_FLAG_LATENCY_SYS		(2 << 0)
>  
>  enum pm_qos_type {
>  	PM_QOS_UNITIALIZED,
> 
> -- 
> 2.47.3
> 
> 

  reply	other threads:[~2026-06-30 21:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 19:59 [PATCH v3 0/4] PM: QoS/pmdomains: support resume latencies for system-wide PM Kevin Hilman (TI)
2026-06-11 19:59 ` [PATCH v3 1/4] PM / QoS: add flag to indicate latency applies system-wide Kevin Hilman (TI)
2026-06-30 21:11   ` Kendall Willis [this message]
2026-06-11 19:59 ` [PATCH v3 2/4] PM / QoS: add lockless read for flags Kevin Hilman (TI)
2026-06-30 21:12   ` Kendall Willis
2026-07-10 10:42   ` Rafael J. Wysocki (Intel)
2026-08-19 16:27     ` Kevin Hilman
2026-06-11 19:59 ` [PATCH v3 3/4] pmdomain: core: add genpd_for_each_child() helper Kevin Hilman (TI)
2026-06-30 21:13   ` Kendall Willis
2026-06-11 19:59 ` [PATCH v3 4/4] pmdomain: add support system-wide resume latency constraints Kevin Hilman (TI)
2026-07-01 17:01   ` Kendall Willis

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=20260630211112.eqagovk2y5uhdbkw@uda0506412 \
    --to=k-willis@ti.com \
    --cc=d-gole@ti.com \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ulfh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox