From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Weikang Guo <guoweikang.kernel@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [QUESTION] Plans for GDIX1003 Support in Goodix Touchscreen Driver
Date: Mon, 24 Feb 2025 22:04:49 -0800 [thread overview]
Message-ID: <Z71dgXzq_utoDqd7@google.com> (raw)
In-Reply-To: <CAOm6qnnhR9++REgtjhZpqNXkBbBAZsGAY8Oy89cXUF9S=Vy-9Q@mail.gmail.com>
Hi Weikang,
On Tue, Feb 25, 2025 at 10:04:41AM +0800, Weikang Guo wrote:
> Hi Bastien, Hans, Dmitry,
>
> I am currently working on the Ayaneo Flip DS device, which I installed Kali
> Linux with kernel version 6.8.11-amd. This device has two touchscreens,
> but only one is functional. After investigating, I found that the second
> touchscreen has the device ID GDIX1003(confirmed by exporting the results
> through acpidump), and upon comparing with the current driver, I noticed
> that only GDIX1001, GDIX1002, and GDX9110 are supported.
>
> I would like to inquire about the following:
>
> Is there any ongoing development or plans to add support for the GDIX1003
> touchscreen in the Goodix driver?
Nothing on my side, sorry.
Thanks.
--
Dmitry
next parent reply other threads:[~2025-02-25 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOm6qnnhR9++REgtjhZpqNXkBbBAZsGAY8Oy89cXUF9S=Vy-9Q@mail.gmail.com>
2025-02-25 6:04 ` Dmitry Torokhov [this message]
2025-02-25 12:09 ` [QUESTION] Plans for GDIX1003 Support in Goodix Touchscreen Driver Hans de Goede
2025-02-27 11:36 ` Weikang Guo
2025-03-01 11:36 ` Hans de Goede
2025-10-13 7:08 ` Salvatore Bonaccorso
2025-10-13 12:15 ` Hans de Goede
2025-02-25 2:44 Weikang Guo
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 2:44 Weikang Guo
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=Z71dgXzq_utoDqd7@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=guoweikang.kernel@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@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