From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org,
Andrew Duggan <aduggan@synaptics.com>,
Lyude Paul <thatslyude@gmail.com>,
Damjan Georgievski <gdamjan@gmail.com>,
Masaki Ota <masaki.ota@jp.alps.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: synaptics_rmi4 - register F03 port as pass-through serio
Date: Wed, 7 Jun 2017 09:59:53 -0700 [thread overview]
Message-ID: <20170607165953.GB13116@dtor-ws> (raw)
In-Reply-To: <20170607070255.GA16591@mail.corp.redhat.com>
On Wed, Jun 07, 2017 at 09:02:55AM +0200, Benjamin Tissoires wrote:
> On Jun 06 2017 or thereabouts, Dmitry Torokhov wrote:
> > The 5th generation Thinkpad X1 Carbons use Synaptics touchpads accessible
> > over SMBus/RMI, combined with ALPS or Elantech trackpoint devices instead
> > of classic IBM/Lenovo trackpoints. Unfortunately there is no way for ALPS
> > driver to detect whether it is dealing with touchpad + trackpoint
> > combination or just a trackpoint, so we end up with a "phantom" dualpoint
> > ALPS device in addition to real touchpad and trackpoint.
> >
> > Given that we do not have any special advanced handling for ALPS or
> > Elantech trackpoints (unlike IBM trackpoints that have separate driver and
> > a host of options) we are better off keeping the trackpoints in PS/2
> > emulation mode. We achieve that by setting serio type to SERIO_PS_PSTHRU,
> > which will limit number of protocols psmouse driver will try. In addition
> > to getting rid of the "phantom" touchpads, this will also speed up probing
> > of F03 pass-through port.
> >
> > Reported-by: Damjan Georgievski <gdamjan@gmail.com>
> > Suggested-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
>
> Thanks for the extensive commit message :)
>
> Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Thanks Benjamin.
Damjan, could you please try this patch too before I send it Linus-wards.
>
> (tested on a t450s without problems).
>
> Cheers,
> Benjamin
>
> > drivers/input/rmi4/rmi_f03.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/rmi4/rmi_f03.c b/drivers/input/rmi4/rmi_f03.c
> > index 77dad045a468..ad71a5e768dc 100644
> > --- a/drivers/input/rmi4/rmi_f03.c
> > +++ b/drivers/input/rmi4/rmi_f03.c
> > @@ -146,7 +146,7 @@ static int rmi_f03_register_pt(struct f03_data *f03)
> > if (!serio)
> > return -ENOMEM;
> >
> > - serio->id.type = SERIO_8042;
> > + serio->id.type = SERIO_PS_PSTHRU;
> > serio->write = rmi_f03_pt_write;
> > serio->port_data = f03;
> >
> > --
> > 2.13.0.506.g27d5fe0cd-goog
> >
> >
> > --
> > Dmitry
--
Dmitry
next prev parent reply other threads:[~2017-06-07 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 6:51 [PATCH] Input: synaptics_rmi4 - register F03 port as pass-through serio Dmitry Torokhov
2017-06-07 7:02 ` Benjamin Tissoires
2017-06-07 16:59 ` Dmitry Torokhov [this message]
2017-06-08 11:58 ` Damjan Georgievski
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=20170607165953.GB13116@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=gdamjan@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masaki.ota@jp.alps.com \
--cc=thatslyude@gmail.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).