[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220325054228.5247-1-mario.limonciello@amd.com>
Date: Fri, 25 Mar 2022 00:42:25 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Huang Rui <ray.huang@....com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>
CC: "open list:AMD PSTATE DRIVER" <linux-pm@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Mario Limonciello <mario.limonciello@....com>
Subject: [PATCH 0/3] Improve usability for amd-pstate
There has recently been some news coverage about `amd-pstate` being in
5.17, but this news also mentioned that it's a bit difficult to use.
You need to either block init calls, or compile the module into the kernel
to force it to take precedence over acpi-cpufreq.
This series aims to improve the usability of amd-pstate so that distros
can compile as a module, but users can still use it (relatively) easily.
A new module parameter is included that will force amd-pstate to take
precedence and a module table to let it load automatically on such systems.
With the patches in this series a user can make a file
/etc/modprobe.d/amd-pstate.conf:
options amd-pstate replace=1
Then upon the next reboot amd-pstate should load automatically even if
acpi-cpufreq was included on the system.
Mario Limonciello (3):
cpufreq: Allow passing NULL as the argument for unregistering a driver
cpufreq: amd-pstate: Allow replacing existing cpufreq drivers when
loaded
cpufreq: amd-pstate: Add a module device table
drivers/cpufreq/amd-pstate.c | 19 ++++++++++++++++---
drivers/cpufreq/cpufreq.c | 4 ++--
2 files changed, 18 insertions(+), 5 deletions(-)
--
2.34.1
Powered by blists - more mailing lists