From: Hans de Goede <hdegoede@redhat.com>
To: Felix Engelhardt <felix.engelhardt@eidu.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/input/touchscreen/goodix.c: Add support for ACPI ID GDX9110
Date: Mon, 7 Aug 2023 19:08:09 +0200 [thread overview]
Message-ID: <79004399-65df-01ed-faa7-5dd6c3cbb75d@redhat.com> (raw)
In-Reply-To: <20230807124723.382899-1-felix.engelhardt@eidu.com>
Hi,
On 8/7/23 14:47, Felix Engelhardt wrote:
> The Goodix touchscreen controller with ACPI ID GDX9110 was not recognized
> by the goodix driver. This patch adds this ID to the list of supported IDs,
> allowing the driver to be used with this device. The change will allow
> Linux to be used on ~1 million tablet devices used in Kenyan primary
> schools.
>
> Signed-off-by: Felix Engelhardt <felix.engelhardt@eidu.com>
> ---
> drivers/input/touchscreen/goodix.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/input/touchscreen/goodix.c b/drivers/input/touchscreen/goodix.c
> index 4f53d3c57e69..9cdc01eb00c9 100644
> --- a/drivers/input/touchscreen/goodix.c
> +++ b/drivers/input/touchscreen/goodix.c
> @@ -1379,6 +1379,7 @@ MODULE_DEVICE_TABLE(i2c, goodix_ts_id);
> static const struct acpi_device_id goodix_acpi_match[] = {
> { "GDIX1001", 0 },
> { "GDIX1002", 0 },
> + { "GDX9110", 0 },
> { }
> };
> MODULE_DEVICE_TABLE(acpi, goodix_acpi_match);
Hmm, GDX without the 'I' does look like an official ACPI vendor prefix. But if this is used in the wild, then I guess we'll just need to live with it:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
next prev parent reply other threads:[~2023-08-07 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 12:47 [PATCH] drivers/input/touchscreen/goodix.c: Add support for ACPI ID GDX9110 Felix Engelhardt
2023-08-07 17:08 ` Hans de Goede [this message]
2023-08-15 18:39 ` 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=79004399-65df-01ed-faa7-5dd6c3cbb75d@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=felix.engelhardt@eidu.com \
--cc=hadess@hadess.net \
--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).