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>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/4] PM / QoS: add lockless read for flags
Date: Tue, 25 Aug 2026 11:19:10 -0500 [thread overview]
Message-ID: <20260825161910.3y6avivkn6layuyi@uda0506412> (raw)
In-Reply-To: <20260819-topic-lpm-pmdomain-device-constraints-v4-2-7ceb095f5474@baylibre.com>
On 10:08-20260819, Kevin Hilman (TI) wrote:
> Add a lockless read for QoS flags similar to the lockless read for
> resume latency (dev_pm_qos_raw_resume_latency) which may be called
> from atomic context (e.g. genpd governors running under a raw spinlock
> or in the syscore suspend path), where taking that sleeping lock would
> be invalid on PREEMPT_RT.
>
> dev_pm_qos_raw_flags() now reads dev->power.qos->flags.effective_flags
> with READ_ONCE() so also add corresponding WRITE_ONCE() to the two
> effective_flags writes, the same way pm_qos_set_value() already does
> for target_value/pm_qos_read_value().
>
> Signed-off-by: Kevin Hilman (TI) <khilman@baylibre.com>
Reviewed-by: Kendall Willis <k-willis@ti.com>
next prev parent reply other threads:[~2026-08-25 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 17:08 [PATCH v4 0/4] PM: QoS/pmdomains: support resume latencies for system-wide PM Kevin Hilman (TI)
2026-08-19 17:08 ` [PATCH v4 1/4] PM / QoS: add flag to indicate latency applies system-wide Kevin Hilman (TI)
2026-08-25 16:17 ` Kendall Willis
2026-08-19 17:08 ` [PATCH v4 2/4] PM / QoS: add lockless read for flags Kevin Hilman (TI)
2026-08-25 16:19 ` Kendall Willis [this message]
2026-08-19 17:08 ` [PATCH v4 3/4] pmdomain: core: add genpd_for_each_child() helper Kevin Hilman (TI)
2026-08-19 17:22 ` Abel Vesa
2026-08-26 21:59 ` Kevin Hilman
2026-08-19 17:08 ` [PATCH v4 4/4] pmdomain: add support system-wide resume latency constraints Kevin Hilman (TI)
2026-08-19 17:28 ` Abel Vesa
2026-08-25 16:19 ` 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=20260825161910.3y6avivkn6layuyi@uda0506412 \
--to=k-willis@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