From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215177] Stop exporting platform_profile interface for Lenovo T14/P14s Gen2 AMD
Date: Tue, 30 Nov 2021 21:16:25 +0000 [thread overview]
Message-ID: <bug-215177-215701-OgwHqVKb0i@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215177-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215177
mario.limonciello@amd.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mario.limonciello@amd.com
--- Comment #1 from mario.limonciello@amd.com ---
It's fortunate that it's a noop right now and not causing a performance
degradation. Presumably these systems DYTC interface *does* work on Windows
though, and with the modified calls right?
I suppose there are two short term ways to approach this:
1) Quirk thinkpad_acpi to these systems/ broken BIOS versions to disable
platform profiles. This assumes it will be fixed in a future BIOS version.
2) Quirk thinkpad_acpi to use the corrected argument mapping on these systems,
mentioned in that linked issue.
IMO between those two options the second sounds better.
In the longer term though I think the discrepancy of expectations needs to be
fixed in thinkpad_acpi.
--
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:[~2021-11-30 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 16:20 [Bug 215177] New: Stop exporting platform_profile interface for Lenovo T14/P14s Gen2 AMD bugzilla-daemon
2021-11-30 21:16 ` bugzilla-daemon [this message]
2021-11-30 22:25 ` [Bug 215177] " bugzilla-daemon
2021-12-01 3:16 ` bugzilla-daemon
2022-07-07 19:44 ` bugzilla-daemon
2022-07-07 19:45 ` 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-215177-215701-OgwHqVKb0i@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.