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: [email protected]
>
> 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
