linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 24 Nov 2023 20:45:28 -0800	[thread overview]
Message-ID: <ZWF76ALANQwP_9b1@google.com> (raw)
In-Reply-To: <20230925163313.1.I55bfb5880d6755094a995d3ae44c13810ae98be4@changeid>

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

  parent reply	other threads:[~2023-11-25  4:45 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 [this message]
2023-11-27 16:38   ` Jonathan Denose
2024-01-08 16:36     ` Jonathan Denose
2024-01-09 19:28     ` Dmitry Torokhov
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=ZWF76ALANQwP_9b1@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;
as well as URLs for NNTP newsgroup(s).