From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ulrik De Bie <ulrik.debie-os@e2big.org>
Cc: Arjan Opmeer <arjan@opmeer.net>, linux-input@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Input: elantech - add Fujitsu Lifebook E546/E557 to force crc_enabled
Date: Wed, 7 Jun 2017 10:31:22 -0700 [thread overview]
Message-ID: <20170607173122.GF13116@dtor-ws> (raw)
In-Reply-To: <20170531184942.23214-1-ulrik.debie-os@e2big.org>
On Wed, May 31, 2017 at 08:49:42PM +0200, Ulrik De Bie wrote:
> The Lifebook E546 and E557 touchpad were also not functioning and
> worked after running:
>
> echo "1" > /sys/devices/platform/i8042/serio2/crc_enabled
>
> Add them to the list of machines that need this workaround.
>
> Signed-off-by: Ulrik De Bie <ulrik.debie-os@e2big.org>
> Reviewed-by: Arjan Opmeer <arjan@opmeer.net>
Applied, thank you.
> ---
> drivers/input/mouse/elantech.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> The problem was reported by users of those laptops and they confirmed that
> the crc_enabled workaround solved it. They were not able to test the patch
> though so if anyone else here has such a laptop please feel free to test
> the patch !
>
> diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
> index e73d968023f7..f1fa1f172107 100644
> --- a/drivers/input/mouse/elantech.c
> +++ b/drivers/input/mouse/elantech.c
> @@ -1118,8 +1118,10 @@ 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 E546 0x470f00 50, 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 LIFEBOOK E557 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 (**)
> * Gigabyte U2442 0x450f01 58, 17, 0c 2 hw buttons
> @@ -1525,6 +1527,13 @@ static const struct dmi_system_id elantech_dmi_force_crc_enabled[] = {
> },
> },
> {
> + /* Fujitsu LIFEBOOK E546 does not work with crc_enabled == 0 */
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK E546"),
> + },
> + },
> + {
> /* Fujitsu LIFEBOOK E547 does not work with crc_enabled == 0 */
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> @@ -1546,6 +1555,13 @@ static const struct dmi_system_id elantech_dmi_force_crc_enabled[] = {
> },
> },
> {
> + /* Fujitsu LIFEBOOK E557 does not work with crc_enabled == 0 */
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK E557"),
> + },
> + },
> + {
> /* Fujitsu LIFEBOOK U745 does not work with crc_enabled == 0 */
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> --
> 2.11.0
>
--
Dmitry
prev parent reply other threads:[~2017-06-07 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 18:49 [PATCH v1 1/1] Input: elantech - add Fujitsu Lifebook E546/E557 to force crc_enabled Ulrik De Bie
2017-06-07 17:31 ` 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=20170607173122.GF13116@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=arjan@opmeer.net \
--cc=linux-input@vger.kernel.org \
--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).