From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 217947] WARNING at drivers/acpi/platform_profile.c:74 in platform_profile_show()
Date: Tue, 26 Sep 2023 10:32:09 +0000 [thread overview]
Message-ID: <bug-217947-215701-xB8yJNopPk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217947-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217947
--- Comment #4 from Jiri Slaby (jirislaby@gmail.com) ---
(In reply to Jiri Slaby from comment #3)
> > As a quick test could you try adding:
> >
> > /* Check if we are PSC mode, or have AMT enabled */
> > funcmode = (output >> DYTC_GET_FUNCTION_BIT) & 0xF;
> > +if (funcmode == DYTC_FUNCTION_STD)
> > + funcmode = DYTC_FUNCTION_PSC;
> >
> > To see if it behaves correctly please?
>
> Will try.
It only changes the error to EINVAL. 0xf is not handled as a correct state in
PSC.
BTW the first (bad) log:
thinkpad_acpi: dytc_profile_refresh: err=-22 mmc=0 psc=1 mmc_get=0 funcmode=13
output=0x1f001 perfmode=15
subsequent refreshes (good):
thinkpad_acpi: dytc_profile_refresh: err=0 mmc=0 psc=1 mmc_get=0 funcmode=13
output=0x20013d01 perfmode=3
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-09-26 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 9:12 [Bug 217947] New: WARNING at drivers/acpi/platform_profile.c:74 in platform_profile_show() bugzilla-daemon
2023-09-25 9:12 ` [Bug 217947] " bugzilla-daemon
2023-09-25 12:54 ` bugzilla-daemon
2023-09-26 6:54 ` bugzilla-daemon
2023-09-26 6:57 ` bugzilla-daemon
2023-09-26 10:32 ` bugzilla-daemon [this message]
2023-09-27 0:06 ` bugzilla-daemon
2023-09-27 6:34 ` bugzilla-daemon
2023-09-27 17:09 ` bugzilla-daemon
2023-09-28 6:10 ` bugzilla-daemon
2023-10-26 8:59 ` bugzilla-daemon
2023-10-26 17:21 ` 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-217947-215701-xB8yJNopPk@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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