From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input - elan_i2c: remove Lenovo Legion Y7000 PnpID
Date: Fri, 6 Sep 2019 12:03:34 -0700 [thread overview]
Message-ID: <20190906190334.GP187474@dtor-ws> (raw)
In-Reply-To: <20190906085948.27470-1-benjamin.tissoires@redhat.com>
On Fri, Sep 06, 2019 at 10:59:48AM +0200, Benjamin Tissoires wrote:
> Looks like the Bios of the Lenovo Legion Y7000 is using ELAN061B
> when the actual device is supposed to be used with hid-multitouch.
>
> Remove it from the list of the supported device, hoping that
> no one will complain about the loss in functionality.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=203467
> Fixes: Fixes: 738c06d0e456 ("Input: elan_i2c - add hardware ID for multiple Lenovo laptops")
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
I suppose this one should go to stable?
> ---
>
> Note to self: once this gets in, we need to send a similar patch
> to stable, as there are a few stable branches with this PnpID.
>
>
> include/linux/input/elan-i2c-ids.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/input/elan-i2c-ids.h b/include/linux/input/elan-i2c-ids.h
> index ceabb01a6a7d..1ecb6b45812c 100644
> --- a/include/linux/input/elan-i2c-ids.h
> +++ b/include/linux/input/elan-i2c-ids.h
> @@ -48,7 +48,7 @@ static const struct acpi_device_id elan_acpi_id[] = {
> { "ELAN0618", 0 },
> { "ELAN0619", 0 },
> { "ELAN061A", 0 },
> - { "ELAN061B", 0 },
> +/* { "ELAN061B", 0 }, not working on the Lenovo Legion Y7000 */
> { "ELAN061C", 0 },
> { "ELAN061D", 0 },
> { "ELAN061E", 0 },
> --
> 2.21.0
>
--
Dmitry
next prev parent reply other threads:[~2019-09-06 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 8:59 [PATCH] Input - elan_i2c: remove Lenovo Legion Y7000 PnpID Benjamin Tissoires
2019-09-06 19:03 ` Dmitry Torokhov [this message]
2019-09-06 19:09 ` Dmitry Torokhov
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=20190906190334.GP187474@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).