[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250527-userspace-governor-doc-v2-0-0e22c69920f2@sony.com>
Date: Tue, 27 May 2025 21:59:08 +0900
From: Shashank Balaji <shashank.mahadasyam@...y.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>, Jonathan Corbet <corbet@....net>
Cc: linux-pm@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Shinya Takumi <shinya.takumi@...y.com>,
20250522-userspace-governor-doc-v1-1-c8a038e39084@...y.com,
Shashank Balaji <shashank.mahadasyam@...y.com>
Subject: [PATCH v2 0/2] cpufreq: userspace: add CPUFREQ_GOV_STRICT_TARGET
flag
In-Reply-To: 20250522-userspace-governor-doc-v1-1-c8a038e39084@...y.com
Signed-off-by: Shashank Balaji <shashank.mahadasyam@...y.com>
---
Changes in v2:
- Instead of modifying the documentation to say that variation in frequency is
possible despite setting scaling_setspeed, add the CPUFREQ_GOV_STRICT_TARGET
flag to the userspace governor to make its behaviour match the expectation when
used with the intel_pstate driver with HWP enabled
- Mention in the documentation that variation in frequency due to hardware
factors is possible
- Link to v1: https://lore.kernel.org/r/20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com
---
Shashank Balaji (2):
cpufreq: userspace: set CPUFREQ_GOV_STRICT_TARGET flag
cpufreq, docs: userspace: mention variation in freq due to hw coordination
Documentation/admin-guide/pm/cpufreq.rst | 4 +++-
drivers/cpufreq/cpufreq_userspace.c | 1 +
2 files changed, 4 insertions(+), 1 deletion(-)
---
base-commit: 914873bc7df913db988284876c16257e6ab772c6
change-id: 20250522-userspace-governor-doc-86380dbab3d5
Best regards,
--
Shashank Balaji <shashank.mahadasyam@...y.com>
Powered by blists - more mailing lists