linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Benjamin Tissoires <btissoir@redhat.com>,
	linux-input <linux-input@vger.kernel.org>
Cc: Manyi Li <limanyi@uniontech.com>
Subject: Detecting if a laptop is using a i2c/smbus or a ps/2 attached touchpad?
Date: Mon, 7 Nov 2022 11:10:16 +0100	[thread overview]
Message-ID: <ae50236e-1ce8-b526-9c17-7bc0463ebb86@redhat.com> (raw)

Hi Benjamin, et. al.,

I have just merged a patch which adds a couple of DMI quirks to disable
the touchpad on/off functionality of the ideapad-laptop module on some models,
because it is causing issues there.

Patch:      https://lore.kernel.org/platform-driver-x86/20221018095323.14591-1-limanyi@uniontech.com/
Discussion: https://lore.kernel.org/platform-driver-x86/fdceb6d2-c38c-e8ff-4c19-b01521ca46c0@redhat.com/

Rather then using DMI quirks I would prefer to just disable it everywhere
where a i2c-attached touchpad is used. Be it either one only attached to
i2c, or one of the synaptics intertouch thingies. I'm still trying to
figure out why the ideapad-laptop module's touchpad control (which
uses the EC + enabling/disabling the i8042 aux-port) matters for
i2c-attached touchpads at all, so I suspect that intertouch might be
a part of it.

So now I'm wondering if there is some nice way for the ideapad-laptop
code to check if the touchpad is intertouch and/or if it is i2c-attached
only ...

Any ideas?

Regards,

Hans

p.s.

Is it possible that Elan touchpads use something similar to intertouch,
or is that a synaptics thing only (under Linux)  ?


             reply	other threads:[~2022-11-07 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 10:10 Hans de Goede [this message]
2022-11-07 10:52 ` Detecting if a laptop is using a i2c/smbus or a ps/2 attached touchpad? Benjamin Tissoires
2022-11-07 12:21   ` Hans de Goede

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=ae50236e-1ce8-b526-9c17-7bc0463ebb86@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=btissoir@redhat.com \
    --cc=limanyi@uniontech.com \
    --cc=linux-input@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).