From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Maxim Mikityanskiy" <maxtram95@gmail.com>,
"Ike Panhc" <ike.pan@canonical.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org,
"Jonathan Denose" <jdenose@chromium.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86: ideapad-laptop: Stop calling i8042_command()
Date: Mon, 12 Aug 2024 20:18:24 +0200 [thread overview]
Message-ID: <2d5be262-3bfd-4b66-bee4-97c89a9a4707@redhat.com> (raw)
In-Reply-To: <ZrpFSnCQ0T4_7zAB@google.com>
Hi Dmitry,
On 8/12/24 7:24 PM, Dmitry Torokhov wrote:
> On Mon, Aug 12, 2024 at 04:41:50PM +0200, Hans de Goede wrote:
>> Hi Maxim,
>>
>> On 8/12/24 4:37 PM, Maxim Mikityanskiy wrote:
>>> On Mon, 05 Aug 2024 at 17:45:19 +0200, Hans de Goede wrote:
>>>> On 8/5/24 5:30 PM, Maxim Mikityanskiy wrote:
>>>>> That means, userspace is not filtering out events upon receiving
>>>>> KEY_TOUCHPAD_OFF. If we wanted to rely on that, we would need to send
>>>>> KEY_TOUCHPAD_TOGGLE from the driver, but we actually can't, because Z570
>>>>> is weird. It maintains the touchpad state in firmware to light up the
>>>>> status LED, but the firmware doesn't do the actual touchpad disablement.
>>>>>
>>>>> That is, if we use TOGGLE, the LED will get out of sync. If we use
>>>>> ON/OFF, the touchpad won't be disabled, unless we do it in the kernel.
>>>>
>>>> Ack.
>>>>
>>>> So how about this instead:
>>>>
>>>> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
>>>> index 1ace711f7442..b7fa06f793cb 100644
>>>> --- a/drivers/platform/x86/ideapad-laptop.c
>>>> +++ b/drivers/platform/x86/ideapad-laptop.c
>>>> @@ -1574,7 +1574,7 @@ static void ideapad_sync_touchpad_state(struct ideapad_private *priv, bool send_
>>>> * touchpad off and on. We send KEY_TOUCHPAD_OFF and
>>>> * KEY_TOUCHPAD_ON to not to get out of sync with LED
>>>> */
>>>> - if (priv->features.ctrl_ps2_aux_port)
>>>> + if (send_events && priv->features.ctrl_ps2_aux_port)
>>>> i8042_command(¶m, value ? I8042_CMD_AUX_ENABLE : I8042_CMD_AUX_DISABLE);
>>>>
>>>> /*
>>>>
>>>> Maxmime, if you still have your Z570 can you check if the touchpad state after a suspend/resume
>>>> correctly reflects the state before suspend/resume in both touchpad on / off states ?
>>>
>>> *Maxim
>>
>> Oops, sorry.
>>
>>> Just a heads-up, my Z570 now belongs to a family member, we'll test what
>>> you asked, but right now there is a btrfs corruption on that laptop that
>>> we need to fix first, it interferes with kernel compilation =/
>>
>> Note as discussed in another part of the thread the original bug report
>> actually was not on a Z570, so the whole usage of i8042_command() on
>> suspend/resume was a bit of a red herring. And the suspend/resume issue
>> has been fixed in another way in the mean time.
>>
>> So there really is no need to test this change anymore. At the moment
>> there are no planned changes to ideapad-laptop related to this.
>
> I think we still need to stop ideapad-laptop poking into 8042,
> especially ahead of time.
I agree. I think your suggestion of using the new(ish) [un]inhibit
support in the input subsystem for this instead of poking at the i8042
is a good idea.
As I mentioned when you first suggested this, I guess this requires 2 things:
1. Some helper to find the struct input_dev for the input_dev related
to the ps/2 aux port
2. In kernel API / functions to do inhibit/uninhibit
(maybe these already exist?)
> If we do not want to wait for userspace to
> handle this properly, I wonder if we could not create an
> input_handler that would attach to the touchpad device and filter out
> all events coming from the touchpad if touchpad is supposed to be off.
I think using the inhibit stuff would be better no?
The biggest problems with trying to fix this are:
1. Finding time to work on this
2. Finding someone willing to test the patches
Finding the time is going to be an issue for me since the i8042_command()
calls are only still done on a single model laptop (using a DMI quirk)
inside ideapad-laptop now, so this is pretty low priority IMHO. Which
in practice means that I will simply never get around to this, sorry...
Regards,
Hans
next prev parent reply other threads:[~2024-08-12 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:16 [PATCH] platform/x86: ideapad-laptop: Stop calling i8042_command() Hans de Goede
2024-08-05 14:30 ` Dmitry Torokhov
2024-08-05 15:30 ` Maxim Mikityanskiy
2024-08-05 15:45 ` Hans de Goede
2024-08-05 17:00 ` Dmitry Torokhov
2024-08-05 18:40 ` Hans de Goede
2024-08-12 14:37 ` Maxim Mikityanskiy
2024-08-12 14:41 ` Hans de Goede
2024-08-12 17:24 ` Dmitry Torokhov
2024-08-12 18:18 ` Hans de Goede [this message]
2024-08-12 19:26 ` Dmitry Torokhov
2024-08-18 20:30 ` Dmitry Torokhov
2024-08-20 10:46 ` Maxim Mikityanskiy
2024-08-20 21:40 ` Maxim Mikityanskiy
2024-08-21 5:28 ` Dmitry Torokhov
2024-09-03 23:55 ` Dmitry Torokhov
2024-09-22 8:35 ` Maxim Mikityanskiy
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=2d5be262-3bfd-4b66-bee4-97c89a9a4707@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ike.pan@canonical.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdenose@chromium.org \
--cc=linux-input@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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).