From: Alex Yeo <alexyeo362@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: "Kenneth Chan" <kenneth.t.chan@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [RFC PATCH v8] platform/x86: panasonic-laptop: add fan speed mode for newer models
Date: Sat, 1 Aug 2026 11:13:14 +0800 [thread overview]
Message-ID: <4ac9ffe4-0f14-45d7-9a62-7a5fe7c40bf3@gmail.com> (raw)
In-Reply-To: <20260729044332.382862-1-alexyeo362@gmail.com>
Hello everyone,
Please disregard this patch.
What I have found is not just a fan control method, but a set of methods
to control active and passive cooling policies for the cooling device +
a way to cap processor power and unlock it.
The reverse engineering notes are still relevant, but I had clearly
missed the part where the fan code is in proximity to the code that
toggles the power limit.
Given this, I no longer think this belongs in thermal or hwmon.
platform_profile appears to be the appropriate fit, although I will
continue investigating.
Apologies for the confusion. I will redo the patch with further testing
and data.
If I do move forward with this approach, I plan to submit this as a
completely new patch instead since the current subject "add fan speed
mode for newer models" no longer applies.
Thank you,
Alex
prev parent reply other threads:[~2026-08-01 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 4:43 [RFC PATCH v8] platform/x86: panasonic-laptop: add fan speed mode for newer models Alex Yeo
2026-08-01 3:13 ` Alex Yeo [this message]
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=4ac9ffe4-0f14-45d7-9a62-7a5fe7c40bf3@gmail.com \
--to=alexyeo362@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=justinstitt@google.com \
--cc=kenneth.t.chan@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--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