From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218686] Fail to set energy_performance_preference of amd processor on asus ga403uv
Date: Mon, 05 Aug 2024 13:11:26 +0000 [thread overview]
Message-ID: <bug-218686-137361-n4iDgV3TgC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218686-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218686
--- Comment #73 from Chema (chemasanchezgarabito@gmail.com) ---
Also I see that in the kernel logs when booting it says the following:
☁ ~ sudo dmesg | grep CPPC
[ 1.565705] ACPI CPPC: Parsed CPC struct for CPU: 0
[ 1.565845] ACPI CPPC: Parsed CPC struct for CPU: 1
[ 1.565928] ACPI CPPC: Parsed CPC struct for CPU: 2
[ 1.566022] ACPI CPPC: Parsed CPC struct for CPU: 3
[ 1.566136] ACPI CPPC: Parsed CPC struct for CPU: 4
[ 1.566246] ACPI CPPC: Parsed CPC struct for CPU: 5
[ 1.566365] ACPI CPPC: Parsed CPC struct for CPU: 6
[ 1.566476] ACPI CPPC: Parsed CPC struct for CPU: 7
[ 1.566566] ACPI CPPC: Parsed CPC struct for CPU: 8
[ 1.566651] ACPI CPPC: Parsed CPC struct for CPU: 9
[ 1.566736] ACPI CPPC: Parsed CPC struct for CPU: 10
[ 1.566844] ACPI CPPC: Parsed CPC struct for CPU: 11
[ 1.566952] ACPI CPPC: Parsed CPC struct for CPU: 12
[ 1.567067] ACPI CPPC: Parsed CPC struct for CPU: 13
[ 1.567191] ACPI CPPC: Parsed CPC struct for CPU: 14
[ 1.567341] ACPI CPPC: Parsed CPC struct for CPU: 15
[ 1.585000] amd_pstate: AMD CPPC shared memory based functionality is
supported
[ 1.586011] ACPI CPPC: _CPC in PCC is not supported
[ 1.586134] ACPI CPPC: _CPC in PCC is not supported
[ 1.586204] ACPI CPPC: _CPC in PCC is not supported
[ 1.586230] ACPI CPPC: _CPC in PCC is not supported
[ 1.586275] ACPI CPPC: _CPC in PCC is not supported
[ 1.586302] ACPI CPPC: _CPC in PCC is not supported
[ 1.586347] ACPI CPPC: _CPC in PCC is not supported
[ 1.586376] ACPI CPPC: _CPC in PCC is not supported
[ 1.586412] ACPI CPPC: _CPC in PCC is not supported
[ 1.586469] ACPI CPPC: _CPC in PCC is not supported
[ 1.586494] ACPI CPPC: _CPC in PCC is not supported
[ 1.586530] ACPI CPPC: _CPC in PCC is not supported
[ 1.586579] ACPI CPPC: _CPC in PCC is not supported
[ 1.586616] ACPI CPPC: _CPC in PCC is not supported
[ 1.586644] ACPI CPPC: _CPC in PCC is not supported
[ 1.586669] ACPI CPPC: _CPC in PCC is not supported
And that logs are thrown in:
- L879 cppc_acpi.c
- L1491 cppc_api.c
And first one means that
/**
* acpi_cppc_processor_probe - Search for per CPU _CPC objects.
* @pr: Ptr to acpi_processor containing this CPU's logical ID.
*
* Return: 0 for success or negative value for err.
*/
int acpi_cppc_processor_probe(struct acpi_processor *pr)
is working correctly
But then "int cppc_set_epp_perf" throwing because of "if
(CPC_IN_PCC(epp_set_reg) || CPC_IN_PCC(auto_sel_reg))" is not met
So can correclty read the CPC object of ACPI but not write with PCC in the CPC
obj?
--
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:[~2024-08-05 13:11 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 2:56 [Bug 218686] New: Fail to set energy_performance_preference of amd processor on asus ga403uv bugzilla-daemon
2024-04-08 1:48 ` [Bug 218686] " bugzilla-daemon
2024-04-10 3:36 ` bugzilla-daemon
2024-04-10 5:28 ` bugzilla-daemon
2024-04-10 5:33 ` bugzilla-daemon
2024-04-10 5:39 ` bugzilla-daemon
2024-04-10 5:41 ` bugzilla-daemon
2024-04-10 5:46 ` bugzilla-daemon
2024-04-10 5:48 ` bugzilla-daemon
2024-04-10 6:17 ` bugzilla-daemon
2024-04-10 6:19 ` bugzilla-daemon
2024-04-10 6:26 ` bugzilla-daemon
2024-04-10 6:27 ` bugzilla-daemon
2024-04-10 6:29 ` bugzilla-daemon
2024-04-10 6:42 ` bugzilla-daemon
2024-04-10 6:43 ` bugzilla-daemon
2024-04-10 6:47 ` bugzilla-daemon
2024-04-10 6:49 ` bugzilla-daemon
2024-04-10 6:51 ` bugzilla-daemon
2024-04-10 6:55 ` bugzilla-daemon
2024-04-10 7:02 ` bugzilla-daemon
2024-04-10 7:12 ` bugzilla-daemon
2024-04-10 7:21 ` bugzilla-daemon
2024-04-10 7:26 ` bugzilla-daemon
2024-04-10 7:27 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-11 4:18 ` bugzilla-daemon
2024-04-11 4:19 ` bugzilla-daemon
2024-04-11 4:20 ` bugzilla-daemon
2024-04-11 5:29 ` bugzilla-daemon
2024-04-11 5:30 ` bugzilla-daemon
2024-04-11 7:25 ` bugzilla-daemon
2024-04-11 9:02 ` bugzilla-daemon
2024-04-11 9:15 ` bugzilla-daemon
2024-04-11 10:09 ` bugzilla-daemon
2024-04-11 11:14 ` bugzilla-daemon
2024-04-11 12:56 ` bugzilla-daemon
2024-04-11 15:53 ` bugzilla-daemon
2024-04-11 15:54 ` bugzilla-daemon
2024-04-15 8:37 ` bugzilla-daemon
2024-04-18 7:36 ` bugzilla-daemon
2024-04-18 7:56 ` bugzilla-daemon
2024-04-18 8:41 ` bugzilla-daemon
2024-04-23 7:03 ` bugzilla-daemon
2024-04-23 7:25 ` bugzilla-daemon
2024-05-17 8:50 ` bugzilla-daemon
2024-05-17 11:53 ` bugzilla-daemon
2024-05-17 15:11 ` bugzilla-daemon
2024-05-20 15:26 ` bugzilla-daemon
2024-05-22 14:39 ` bugzilla-daemon
2024-05-22 14:53 ` bugzilla-daemon
2024-05-22 15:12 ` bugzilla-daemon
2024-05-27 8:12 ` bugzilla-daemon
2024-05-27 8:21 ` bugzilla-daemon
2024-05-27 9:48 ` bugzilla-daemon
2024-05-27 10:09 ` bugzilla-daemon
2024-07-15 23:08 ` bugzilla-daemon
2024-07-19 8:46 ` bugzilla-daemon
2024-07-30 10:32 ` bugzilla-daemon
2024-07-30 18:10 ` bugzilla-daemon
2024-07-30 23:34 ` bugzilla-daemon
2024-07-30 23:38 ` bugzilla-daemon
2024-07-31 5:41 ` bugzilla-daemon
2024-07-31 5:41 ` bugzilla-daemon
2024-07-31 11:50 ` bugzilla-daemon
2024-07-31 11:54 ` bugzilla-daemon
2024-07-31 12:12 ` bugzilla-daemon
2024-08-01 3:39 ` bugzilla-daemon
2024-08-01 12:02 ` bugzilla-daemon
2024-08-03 18:54 ` bugzilla-daemon
2024-08-03 18:56 ` bugzilla-daemon
2024-08-04 15:00 ` bugzilla-daemon
2024-08-04 23:50 ` bugzilla-daemon
2024-08-05 13:11 ` bugzilla-daemon [this message]
2024-08-05 14:32 ` bugzilla-daemon
2024-08-05 20:16 ` bugzilla-daemon
2024-08-06 8:29 ` bugzilla-daemon
2024-08-06 9:11 ` bugzilla-daemon
2024-08-06 14:27 ` bugzilla-daemon
2024-09-08 15:15 ` bugzilla-daemon
2024-09-08 15:33 ` bugzilla-daemon
2024-09-08 15:34 ` bugzilla-daemon
2024-09-09 2:54 ` bugzilla-daemon
2024-09-09 13:54 ` bugzilla-daemon
2024-09-09 14:43 ` bugzilla-daemon
2024-09-09 15:00 ` bugzilla-daemon
2024-09-09 15:02 ` bugzilla-daemon
2024-09-09 15:04 ` bugzilla-daemon
2024-09-09 21:16 ` bugzilla-daemon
2024-09-09 21:18 ` bugzilla-daemon
2024-09-09 21:31 ` bugzilla-daemon
2024-09-09 21:54 ` bugzilla-daemon
2024-09-09 22:06 ` bugzilla-daemon
2024-09-10 0:21 ` bugzilla-daemon
2024-09-10 0:49 ` bugzilla-daemon
2024-09-10 1:20 ` bugzilla-daemon
2024-09-10 1:22 ` bugzilla-daemon
2024-09-10 18:28 ` bugzilla-daemon
2024-09-11 4:32 ` bugzilla-daemon
2024-09-23 15:57 ` bugzilla-daemon
2024-09-23 15:58 ` 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-218686-137361-n4iDgV3TgC@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).