From: "Dave.Wang" <dave.wang@emc.com.tw>
To: "'Dmitry Torokhov'" <dmitry.torokhov@gmail.com>
Cc: <Linux-kernel@vger.kernel.org>, <Linux-input@vger.kernel.org>,
<jingle.wu@emc.com.tw>,
"'Benjamin Tissoires'" <benjamin.tissoires@redhat.com>
Subject: RE: [PATCH] Input: elan_i2c - Add more hardware ID for Lenovo laptop
Date: Mon, 2 Dec 2019 11:07:26 +0800 [thread overview]
Message-ID: <000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw> (raw)
In-Reply-To: <20191202010253.GO248138@dtor-ws>
Hi Dmitry,
List device with its corresponding hardware ID as below patch,
Please check , thanks!
Add more hardware ID for Lenovo laptop.
Signed-off-by: Dave Wang <dave.wang@emc.com.tw>
---
include/linux/input/elan-i2c-ids.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/linux/input/elan-i2c-ids.h
b/include/linux/input/elan-i2c-ids.h
index 1ecb6b45812c..520858d12680 100644
--- a/include/linux/input/elan-i2c-ids.h
+++ b/include/linux/input/elan-i2c-ids.h
@@ -67,8 +67,15 @@ static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN062B", 0 },
{ "ELAN062C", 0 },
{ "ELAN062D", 0 },
+ { "ELAN062E", 0 }, /* Lenovo V340 Whiskey Lake U */
+ { "ELAN062F", 0 }, /* Lenovo V340 Comet Lake U */
{ "ELAN0631", 0 },
{ "ELAN0632", 0 },
+ { "ELAN0633", 0 }, /* Lenovo S145 */
+ { "ELAN0634", 0 }, /* Lenovo V340 Ice lake */
+ { "ELAN0635", 0 }, /* Lenovo V1415-IIL */
+ { "ELAN0636", 0 }, /* Lenovo V1415-Dali */
+ { "ELAN0637", 0 }, /* Lenovo V1415-IGLR */
{ "ELAN1000", 0 },
{ }
};
--
2.17.1
Best regards,
Dave
-----Original Message-----
From: Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com]
Sent: Monday, December 2, 2019 9:03 AM
To: Dave.Wang <dave.wang@emc.com.tw>
Cc: Linux-kernel@vger.kernel.org; Linux-input@vger.kernel.org;
jingle.wu@emc.com.tw; Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] Input: elan_i2c - Add more hardware ID for Lenovo
laptop
Hi Dave,
On Mon, Nov 25, 2019 at 04:12:56PM +0800, Dave.Wang wrote:
> Add more hardware ID for Lenovo laptop.
Any chance you could also list what devices use which hardware ID?
Thanks!
>
> Signed-off-by: Dave Wang <dave.wang@emc.com.tw>
> ---
> include/linux/input/elan-i2c-ids.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/input/elan-i2c-ids.h
> b/include/linux/input/elan-i2c-ids.h
> index 1ecb6b45812c..247e3f75bae7 100644
> --- a/include/linux/input/elan-i2c-ids.h
> +++ b/include/linux/input/elan-i2c-ids.h
> @@ -67,8 +67,15 @@ static const struct acpi_device_id elan_acpi_id[] = {
> { "ELAN062B", 0 },
> { "ELAN062C", 0 },
> { "ELAN062D", 0 },
> + { "ELAN062E", 0 },
> + { "ELAN062F", 0 },
> { "ELAN0631", 0 },
> { "ELAN0632", 0 },
> + { "ELAN0633", 0 },
> + { "ELAN0634", 0 },
> + { "ELAN0635", 0 },
> + { "ELAN0636", 0 },
> + { "ELAN0637", 0 },
> { "ELAN1000", 0 },
> { }
> };
> --
> 2.17.1
>
--
Dmitry
next prev parent reply other threads:[~2019-12-02 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 8:12 [PATCH] Input: elan_i2c - Add more hardware ID for Lenovo laptop Dave.Wang
2019-12-02 1:02 ` Dmitry Torokhov
2019-12-02 3:07 ` Dave.Wang [this message]
2020-07-09 5:30 ` '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='000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw' \
--to=dave.wang@emc.com.tw \
--cc=Linux-input@vger.kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jingle.wu@emc.com.tw \
/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).