From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215801] Rmmod'ing amd-pstate doesn't restore acpi-cpufreq
Date: Thu, 21 Sep 2023 08:18:05 +0000 [thread overview]
Message-ID: <bug-215801-137361-WGuteNqqJi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215801-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215801
--- Comment #4 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Perry Yuan(AMD) from comment #3)
> (In reply to Artem S. Tashkinov from comment #2)
> > This is still relevant as of Linux 6.6.
> >
> > Would be great if removing amd-pstate enabled acpi-cpufreq.
>
> Normally the system hardware needs to reinitialize CPPC and low-level power
> management firmware when CPPC driver loading, so it better to change grub
> parameters and reboot again.
> dynamically removing amd-pstate and load acpi_cpufreq probably cause some
> potential issues.
>
> Perry.
Could you add this as a note to the amd pstate driver documentation?
Documentation/admin-guide/pm/amd-pstate.rst
Thank you!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-09-21 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 1:43 [Bug 215801] New: Rmmod'ing amd-pstate doesn't restore acpi-cpufreq bugzilla-daemon
2022-04-11 16:22 ` [Bug 215801] " bugzilla-daemon
2023-09-20 10:54 ` bugzilla-daemon
2023-09-21 5:40 ` bugzilla-daemon
2023-09-21 8:18 ` bugzilla-daemon [this message]
2023-09-27 13:01 ` bugzilla-daemon
2023-09-28 2:31 ` bugzilla-daemon
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=bug-215801-137361-WGuteNqqJi@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.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;
as well as URLs for NNTP newsgroup(s).