From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>,
"'Linux PM'" <linux-pm@vger.kernel.org>
Cc: "'Viresh Kumar'" <viresh.kumar@linaro.org>,
"'Christian Loehle'" <christian.loehle@arm.com>,
"'Zak'" <zakbrightonknight@gmail.com>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Mario Limonciello'" <superm1@kernel.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [PATCH v2 0/3] cpufreq: Fix synchronization with system suspend/resume
Date: Tue, 3 Nov 2026 21:38:53 -0700 [thread overview]
Message-ID: <004d01dd6c16$6580c0c0$30824240$@telus.net> (raw)
In-Reply-To: <6065833.DvuYhMxLoT@rafael.j.wysocki>
On 2026.11.03 12:42 : Rafael wrote:
> Hi,
>
> This is an update of
>
> https://lore.kernel.org/linux-pm/5162355.31r3eYUQgx@rafael.j.wysocki/
>
> that modifies the first two patches in the series (to address Sashiko
> findings) and drops the last one.
>
> This series fixes issues related to the synchronization between cpufreq
> and the intel_pstate driver with system suspend/resume mentioned here:
>
> https://lore.kernel.org/linux-pm/CAJZ5v0hT6aoX4tuJM+rO_5iequFc_7rEXCoaFnHoJBaH3JP4KA@mail.gmail.com/
>
> The first patch actually prevents governor operations from being
> carried out on suspended cpufreq policies.
>
> The second one forces the driver .target() callback to be invoked on
> the first frequency update after cpufreq policy resume.
>
> The third one causes intel_pstate to invalidate the cached last
> P-state value during suspend.
>
> Thanks!
Tested-by: Doug Smythies <dsmythies@telus.net>
Test computer: Test computer: i5-10600K, 6 cores, 12 CPUs, HWP disabled, passive mode.
next prev parent reply other threads:[~2026-11-04 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 19:42 [PATCH v2 0/3] cpufreq: Fix synchronization with system suspend/resume Rafael J. Wysocki
2026-11-03 19:45 ` [PATCH v2 1/3] cpufreq: Improve suspend-resume synchronization Rafael J. Wysocki
2026-11-18 13:03 ` [REGRESSION: " Borah, Chaitanya Kumar
2026-11-03 19:47 ` [PATCH v2 2/3] cpufreq: Force passing target frequency to driver during resume Rafael J. Wysocki
2026-11-04 11:56 ` Christian Loehle
2026-11-04 13:44 ` Rafael J. Wysocki (Intel)
2026-11-04 15:09 ` Christian Loehle
2026-11-04 15:46 ` Rafael J. Wysocki (Intel)
2026-11-03 19:49 ` [PATCH v2 3/3] cpufreq: intel_pstate: Clear last written P-state value on suspend Rafael J. Wysocki
2026-11-03 20:06 ` [PATCH v2 0/3] cpufreq: Fix synchronization with system suspend/resume Mario Limonciello
2026-11-03 23:26 ` Zak Brighton Knight
2026-11-04 2:44 ` Zhongqiu Han
2026-11-04 4:19 ` Viresh Kumar
2026-11-04 4:38 ` Doug Smythies [this message]
2026-11-04 12:18 ` Christian Loehle
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='004d01dd6c16$6580c0c0$30824240$@telus.net' \
--to=dsmythies@telus.net \
--cc=christian.loehle@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=superm1@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zakbrightonknight@gmail.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