From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <bentiss@kernel.org>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
Binbin Zhou <zhoubb.aaron@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Jon Xie <jon_xie@pixart.com>, Jay Lee <jay_lee@pixart.com>,
Huacai Chen <chenhuacai@kernel.org>,
linux-input@vger.kernel.org, Xiaotian Wu <wuxiaotian@loongson.cn>
Subject: Re: [PATCH v4] Input: Add driver for PixArt PS/2 touchpad
Date: Tue, 1 Oct 2024 02:04:36 -0700 [thread overview]
Message-ID: <Zvu7JOw0N6XB4ON6@google.com> (raw)
In-Reply-To: <Zvu4mMaOzuL3tDTW@google.com>
On Tue, Oct 01, 2024 at 01:53:44AM -0700, Dmitry Torokhov wrote:
> On Mon, Sep 30, 2024 at 05:59:01PM +0200, Benjamin Tissoires wrote:
> > Hi,
> >
> > On Jul 04 2024, Binbin Zhou wrote:
> > > This patch introduces a driver for the PixArt PS/2 touchpad, which
> > > supports both clickpad and touchpad types.
> > >
> > > At the same time, we extended the single data packet length to 16,
> > > because according to the current PixArt hardware and FW design, we need
> > > 11 bytes/15 bytes to represent the complete three-finger/four-finger data.
> > >
> > > Co-developed-by: Jon Xie <jon_xie@pixart.com>
> > > Signed-off-by: Jon Xie <jon_xie@pixart.com>
> > > Co-developed-by: Jay Lee <jay_lee@pixart.com>
> > > Signed-off-by: Jay Lee <jay_lee@pixart.com>
> > > Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
> >
> > It looks like this new driver made in v6.12-rc1 but is already breaking
> > other touchpads in fedora:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2314756
> >
> > The reported touchpads used to work properly but are now directed to use
> > the PixArt PS2 driver instead of the old one (I would say it should be
> > using Synaptics).
> >
> > I haven't touched PS/2 in a long time, so it's going to be hard to
> > pinpoint the error from my side, but it seems that the new driver is a
> > little bit too greedy.
>
> OK, I gonna revert it and hope PixArt folks will figure out less greedy
> probing sequence (or maybe we need to push it down a few sports).
Although, as I am trying to read the referenced bug, one of the
reporters are saying that they touchpad is USB:
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0
ysFS BusID: 3-3:1.0
Hardware Class: unknown
Model: "Synaptics Unclassified device"
Hotplug: USB
Vendor: usb 0x06cb "Synaptics, Inc."
so I am not sure how PS/2 device would interfere with that.
Could you give me access to the attachments on the bug so I can take a
closer look? And hopefully the original reporter will submit their data.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-10-01 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 12:52 [PATCH v4] Input: Add driver for PixArt PS/2 touchpad Binbin Zhou
2024-07-24 4:31 ` Dmitry Torokhov
2024-07-24 10:00 ` Binbin Zhou
2024-09-30 15:59 ` Benjamin Tissoires
2024-10-01 8:53 ` Dmitry Torokhov
2024-10-01 9:04 ` Dmitry Torokhov [this message]
2024-10-01 9:21 ` Benjamin Tissoires
2024-10-01 11:50 ` Dmitry Torokhov
2024-10-01 12:16 ` Huacai Chen
2024-10-01 13:15 ` Dmitry Torokhov
2024-10-08 10:47 ` Binbin Zhou
2024-10-08 12:48 ` Benjamin Tissoires
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=Zvu7JOw0N6XB4ON6@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=bentiss@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=jay_lee@pixart.com \
--cc=jon_xie@pixart.com \
--cc=linux-input@vger.kernel.org \
--cc=wuxiaotian@loongson.cn \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/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).