From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rong Zhang <i@rong.moe>
Cc: Mark Pearson <mpearson-lenovo@squebb.ca>,
"Derek J. Clark" <derekjohn.clark@gmail.com>,
Ike Panhc <ikepanhc@gmail.com>, Hans de Goede <hansg@kernel.org>,
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>,
Maxim Mikityanskiy <maxtram95@gmail.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] platform/x86: ideapad-laptop: do not poke keyboard controller
Date: Sat, 24 Oct 2026 16:13:50 -0700 [thread overview]
Message-ID: <ab1d30eca12d5e7a764da99b68d0e229@gmail.com> (raw)
In-Reply-To: <5bdb870be988333df200ac7d4904dd1bda6ef52f.camel@rong.moe>
Hi Rong,
On Sat, Oct 24, 2026 at 11:30:06PM +0800, Rong Zhang wrote:
> However, the methodology has been changed from hardware-based to
> software-based. Because of the fundamental change, it has the potential
> to break something if some users depends on the side-effect of toggling
> the aux port.
>
> While my device never needs the quirk, I can think of several useful
> side-effects:
>
> - pause the interrupt (and hence pause event handling) to save some
> energy
> - prevent the touchpad from waking up the platform
> - reset faulty touchpads
>
> By switching to the software-based methodology, all these capabilities
> have gone. Of course, relying on these side-effects is a misuse, but
> relying on the parameter itself without reporting it to the mailing list
> is also a misuse! More below.
This reminds me of https://xkcd.com/1172/ ("Workflow").
Also note that I8042_CMD_AUX_DISABLE / I8042_CMD_AUX_ENABLE only toggles
the AUX clock inhibit bit in the 8042 controller; it does not power down
or reset the touchpad (psmouse is unaware that ideapad-laptop poked the
controller behind its back, which is the whole problem), and i8042
already manages the AUX port and wakeup state across suspend and resume.
> A completely new behavior reusing an old knob is always prone to break
> *something* in a obscure way unless users are notified about the change.
> Breaking something with a visible warning [1] in kmsg is much better than
> potentially breaking something in radio silence.
>
> We don't want to support poking i8042 anymore, so the use of
> 'ctrl_ps2_aux_port' is anyway becoming unsupported. The parameter was
> introduced only for debugging and is expected to be removed at any time.
> If users don't report their use of the parameter to the mailing list,
> they are already relying on a broken setup.
>
> By renaming it and breaking the unsupported setup loudly, we encourage
> users to report quirky devices, as well as getting rid of an outdated
> parameter name.
>
> [1]: ideapad_laptop: unknown parameter 'ctrl_ps2_aux_port' ignored
We already have DMI matching for this quirk (ctrl_ps2_aux_port_list[],
which has only ever contained the 2011 IdeaPad Z570 since commit
c69e7d843d2c added it in 2022), and the module parameter simply sets the
exact same priv->features.ctrl_ps2_aux_port flag as the DMI table.
Intentionally breaking the module parameter for anyone who might be
using it for its intended purpose (making the touchpad toggle hotkey
work on an older IdeaPad) just because of hypothetical spacebar-heating
workflows does not make sense to me.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-10-24 23:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 4:50 Dmitry Torokhov
2026-10-23 9:21 ` Uwe Kleine-König
2026-10-23 16:04 ` Alice Mikityanska
2026-10-23 16:37 ` Alice Mikityanska
2026-10-23 23:05 ` Dmitry Torokhov
2026-10-24 2:15 ` Rong Zhang
2026-10-24 3:20 ` Dmitry Torokhov
2026-10-24 15:30 ` Rong Zhang
2026-10-24 23:13 ` Dmitry Torokhov [this message]
2026-10-25 1:52 ` Rong Zhang
2026-10-25 2:38 ` Dmitry Torokhov
2026-10-25 2:25 ` Rong Zhang
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=ab1d30eca12d5e7a764da99b68d0e229@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=i@rong.moe \
--cc=ikepanhc@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=mpearson-lenovo@squebb.ca \
--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
all inboxes | Powered by JetHome®