From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: ulrik.debie-os@e2big.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2] Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled
Date: Tue, 18 Apr 2017 11:16:02 -0700 [thread overview]
Message-ID: <20170418181602.GA5126@dtor-ws> (raw)
In-Reply-To: <c0e1c192-8a15-91eb-9d93-5fc928f6f04e@leemhuis.info>
On Tue, Apr 18, 2017 at 03:42:55PM +0200, Thorsten Leemhuis wrote:
> Lo! Dmitry, did this fall through the cracks or is there any reason why
> you didn't yet apply below patch? If the latter: What is needed to get
> things moving? Ciao, Thorsten
Sorry, v2 got lost in the thread. Applied now.
>
> On 27.03.2017 10:53, Thorsten Leemhuis wrote:
> > Hi! On 24.03.2017 18:00, Dmitry Torokhov wrote:
> >> On Fri, Mar 24, 2017 at 11:18:51AM +0100, Thorsten Leemhuis wrote:
> >>> Lo! Dmitry, did this fall through the cracks or is there any reason why
> >>> you didn't yet apply below patch? If the latter: What is needed to get
> >>> things moving? Right now I still have access to the machine for further
> >>> tests, but that will change in a week or two. Ciao, Thorsten
> >> I was waiting for an updated version of the patch with updated info for
> >> E547. The "caps" data is coming from Synaptics caps query, so should be
> >> "50, 12, 09".
> >
> > /me opens eyes properly and reads the output from dmesg again
> > /me wonders why he hadn't noticed the capabilities output from the
> > synaptics driver before and missed the obvious connection
> >
> > Many thx for the pointer! Find an updated patch below.
> >
> > Ciao, Thorsten
> >
> > From 8feadc9af68c77c9e0fec3f85b9d5312b8f2e468 Mon Sep 17 00:00:00 2001
> > From: Thorsten Leemhuis <linux@leemhuis.info>
> > Date: Thu, 9 Mar 2017 08:13:21 +0100
> > Subject: Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled
> >
> > Temprary got a Lifebook E547 into my hands and noticed the touchpad
> > only works after running
> >
> > echo "1" > /sys/devices/platform/i8042/serio2/crc_enabled
> >
> > Add it to the list of machines that need this workaround.
> >
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> > Reviewed-by: Ulrik De Bie <ulrik.debie-os@e2big.org>
> > ---
> > drivers/input/mouse/elantech.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
> > index efc8ec3..f53dad0 100644
> > --- a/drivers/input/mouse/elantech.c
> > +++ b/drivers/input/mouse/elantech.c
> > @@ -1118,6 +1118,7 @@ static int elantech_get_resolution_v4(struct psmouse *psmouse,
> > * Asus UX32VD 0x361f02 00, 15, 0e clickpad
> > * Avatar AVIU-145A2 0x361f00 ? clickpad
> > * Fujitsu LIFEBOOK E544 0x470f00 d0, 12, 09 2 hw buttons
> > + * Fujitsu LIFEBOOK E547 0x470f00 50, 12, 09 2 hw buttons
> > * Fujitsu LIFEBOOK E554 0x570f01 40, 14, 0c 2 hw buttons
> > * Fujitsu T725 0x470f01 05, 12, 09 2 hw buttons
> > * Fujitsu H730 0x570f00 c0, 14, 0c 3 hw buttons (**)
> > @@ -1524,6 +1525,13 @@ static int elantech_reconnect(struct psmouse *psmouse)
> > },
> > },
> > {
> > + /* Fujitsu LIFEBOOK E547 does not work with crc_enabled == 0 */
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> > + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK E547"),
> > + },
> > + },
> > + {
> > /* Fujitsu LIFEBOOK E554 does not work with crc_enabled == 0 */
> > .matches = {
> > DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> >
--
Dmitry
prev parent reply other threads:[~2017-04-18 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 8:19 [PATCH] Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled Thorsten Leemhuis
2017-03-09 17:50 ` ulrik.debie-os
2017-03-10 6:53 ` Thorsten Leemhuis
2017-03-24 10:18 ` Thorsten Leemhuis
2017-03-24 17:00 ` Dmitry Torokhov
2017-03-27 8:53 ` [PATCH v2] " Thorsten Leemhuis
2017-04-18 13:42 ` Thorsten Leemhuis
2017-04-18 18:16 ` Dmitry Torokhov [this message]
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=20170418181602.GA5126@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=ulrik.debie-os@e2big.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).