From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jonathan Denose <jdenose@chromium.org>
Cc: linux-input@vger.kernel.org, Jonathan Denose <jdenose@google.com>,
Hans de Goede <hdegoede@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Takashi Iwai <tiwai@suse.de>,
Werner Sembach <wse@tuxedocomputers.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - add quirk for Lenovo ThinkPad T14 Gen 1
Date: Tue, 9 Jan 2024 11:28:54 -0800 [thread overview]
Message-ID: <ZZ2eduF_h7lcBrSL@google.com> (raw)
In-Reply-To: <CALNJtpUHHaq6g0wSuyaNBxtOE9kt6vDzdAGGu6j=JJdJmerDWQ@mail.gmail.com>
Hi Jonathan,
On Mon, Nov 27, 2023 at 10:38:57AM -0600, Jonathan Denose wrote:
> Hi Dmitry
>
> On Fri, Nov 24, 2023 at 10:45 PM Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > Hi Jonathan,
> >
> > On Mon, Sep 25, 2023 at 04:33:20PM -0500, Jonathan Denose wrote:
> > > The ThinkPad T14 Gen 1 touchpad works fine except that clicking
> > > and dragging by tapping the touchpad or depressing the touchpad
> > > do not work. Disabling PNP for controller setting discovery enables
> > > click and drag without negatively impacting other touchpad features.
> >
> > I would like to understand more on how enabling PnP discovery for i8042
> > affects the touchpad. Do you see it using different interrupt or IO
> > ports? What protocol does the touchpad use with/without PnP? If the
> > protocol is the same, do you see difference in the ranges (pressure,
> > etc) reported by the device?
> >
> > Thanks.
> >
> > --
> > Dmitry
>
> Without PnP discovery the touchpad is using the SynPS/2 protocol, with
> PnP discovery, the touchpad is using the rmi4 protocol. Since the
> protocols are different, so are the ranges but let me know if you
> still want to see them.
Thank you for this information. So it is not PnP discovery that appears
harmful in your case, but rather that legacy PS/2 mode appears to be
working better than RMI4 for the device in question.
I will note that the original enablement of RMI4 for T14 was done by
Hans in [1]. Later T14 with AMD were added to the list of devices that
should use RMI4 [2], however this was reverted in [3].
Could you please tell me what exact device you are dealing with? What's
it ACPI ID?
[1] https://lore.kernel.org/all/20201005114919.371592-1-hdegoede@redhat.com/
[2] https://lore.kernel.org/r/20220318113949.32722-1-snafu109@gmail.com
[3] https://lore.kernel.org/r/20220920193936.8709-1-markpearson@lenovo.com
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-01-09 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 21:33 [PATCH] Input: i8042 - add quirk for Lenovo ThinkPad T14 Gen 1 Jonathan Denose
2023-09-26 10:37 ` Hans de Goede
2023-11-21 20:23 ` Jonathan Denose
2023-11-22 15:17 ` Hans de Goede
2023-11-25 4:45 ` Dmitry Torokhov
2023-11-27 16:38 ` Jonathan Denose
2024-01-08 16:36 ` Jonathan Denose
2024-01-09 19:28 ` Dmitry Torokhov [this message]
2024-01-10 23:42 ` Jonathan Denose
2024-01-11 10:48 ` Hans de Goede
2024-01-12 15:10 ` Jonathan Denose
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=ZZ2eduF_h7lcBrSL@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jdenose@chromium.org \
--cc=jdenose@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=tiwai@suse.de \
--cc=wse@tuxedocomputers.com \
/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