Bug#1114557: [regression] 1a8953f4f774 ("HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY") causes issue with ID 4c4a:4155 Jieli Technology USB Composite Device
- To: Staffan Melin <staffan.melin@oscillator.se>, zhangheng <zhangheng@kylinos.cn>
- Cc: Salvatore Bonaccorso <carnil@debian.org>, Jiri Kosina <jkosina@suse.com>, Benjamin Tissoires <bentiss@kernel.org>, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, regressions@lists.linux.dev, stable@vger.kernel.org, 1114557@bugs.debian.org
- Subject: Bug#1114557: [regression] 1a8953f4f774 ("HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY") causes issue with ID 4c4a:4155 Jieli Technology USB Composite Device
- From: Linux Hid <linuxhid@cosmicgizmosystems.com>
- Date: Sun, 28 Sep 2025 17:39:05 -0700
- Message-id: <[🔎] 5101f30a-4f49-4480-9453-1984f6c5a086@cosmicgizmosystems.com>
- Reply-to: Linux Hid <linuxhid@cosmicgizmosystems.com>, 1114557@bugs.debian.org
- In-reply-to: <[🔎] 11f1363dcdec98f4275e4df3145e4f24@oscillator.se>
- References: <[🔎] aL2gYJaXoB6p_oyM@eldamar.lan> <[🔎] c8f3d402-e0ec-4767-b925-d7764aec3d93@kylinos.cn> <[🔎] e81e8d68cb33c7de7b0e353791e21e53@oscillator.se> <[🔎] aMUxHZF-7p7--1qS@eldamar.lan> <[🔎] aMUxg6FLqDetwiGu@eldamar.lan> <[🔎] f08669ec112d6ab2f62e35c0c96d1f06@oscillator.se> <[🔎] 94520aac-2a68-40d2-b188-80f9e361d6de@kylinos.cn> <[🔎] 735c20da-c052-4528-ad91-185a835ca40c@cosmicgizmosystems.com> <[🔎] 54b4b55c-ef29-40ae-a576-0c0b35ea9625@kylinos.cn> <[🔎] 3c299b65351c489fea95ec8b93518b6b@oscillator.se> <[🔎] 01ce8d55-6054-4efa-bed5-ce4c6c6bc0e6@kylinos.cn> <[🔎] 11f1363dcdec98f4275e4df3145e4f24@oscillator.se> <[🔎] 175716941557.2355.4359402692624340645.reportbug@debianduo>
All,
It's good a working solution has been found. I'll comment separately on
the patch submission.
I did some digging to find out why there were multiple devices in the
wild with the same VID:PID.
It seems that Jieli does have a valid USB VID.
Zhuhai Jieli Technology Co., LTD owns VID 13908 (0x3654)
However, in one of their public SDKs they populate the default device
descriptor with:
'J', 'L', // idVendor: 0x4a4c - JL (actually 0x4c4a)
0x55, 0x41, // idProduct: chip id ('U', 'A' 0x4155)
So anyone developing a device using that chip's SDK who doesn't change
the default VID:PID will create a device with 4c4a:4155 VID:PID.
In other SDKs I see a different PID but the same 0x4c4a VID
'5', '4', // idProduct: chip id (0x3435)
So there are probably multiple devices in the wild with 4c4a:3435
VID:PIDs as well.
Here's a link to the 4c4a:4155 SDK if you'd like to take a look.
https://github.com/Jieli-Tech/AW30N/blob/main/sdk/apps/app/bsp/common/usb/device/descriptor.c#L31
Regards,
Terry
On 9/22/2025 11:33 AM, Staffan Melin wrote:
> Thank you,
>
> I can confirm that this patch fixes the touchscreen issue on my GPD DUO.
>
> Tested-by: staffan.melin@oscillator.se
>
> Thank you for your work!
>
> Staffan
>
> On 2025-09-22 11:21, zhangheng wrote:
>> Please help test this patch, I will push it to the kernel community.
>> Currently, the microphone device is functioning normally
Reply to: