linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Staffan Melin <staffan.melin@oscillator.se>
To: Terry Junge <linuxhid@cosmicgizmosystems.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	Zhang Heng <zhangheng@kylinos.cn>, 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: Re: [regression] 1a8953f4f774 ("HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY") causes issue with ID 4c4a:4155 Jieli Technology USB Composite Device
Date: Mon, 08 Sep 2025 11:00:29 +0200	[thread overview]
Message-ID: <a96b110b6b6d9a74506f1cc27cd44b49@oscillator.se> (raw)
In-Reply-To: <36f58d1b-8afe-4895-bef6-59edc791ef0d@cosmicgizmosystems.com>

Hi Terry,

I am the one with the Jieli touchscreen.

On 2025-09-08 06:10, Terry Junge wrote:
> 
> The root of the issue here is that two devices have bootlegged the same 
> VID:PID.
> 
> 0x4c4a is not a valid VID that has been assigned according to the 
> latest list from USBIF (vendor_ids072325_1.pdf) so conflicts like this 
> could surface at any time.
> 
> [   10.188336] usb 3-3: device descriptor read/64, error -71
> [   10.439533] usb 3-3: config 1 interface 0 altsetting 0 has 2 
> endpoint descriptors, different from the interface descriptor's value: 
> 1
> [   10.451534] usb 3-3: New USB device found, idVendor=4c4a, 
> idProduct=4155, bcdDevice= 1.00
> [   10.451540] usb 3-3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [   10.451543] usb 3-3: Product: USB Composite Device
> [   10.451545] usb 3-3: Manufacturer: Jieli Technology
> [   10.451546] usb 3-3: SerialNumber: FFFFFFFFFFFFFFFF
> 
> Can anyone supply the Jieli descriptors, including the Report 
> Descriptor? It clearly has problems but not bad enough to fail 
> enumeration.
> 
> The commit 1a8953f4f774 should be reverted and SMARTLINKTECHNOLOGY 
> should either bootleg a different PID, get a valid VID, or fix their 
> device so a quirk is never required.
> 
> Thanks,
> Terry

In /sys/bus/hid/devices/0003:4C4A:4155.0003 i have the report_descriptor 
file:

00000000  05 0d 09 04 a1 01 85 aa  09 22 a1 00 09 42 15 00  
|........."...B..|
00000010  25 01 75 01 95 01 81 02  75 03 81 03 09 51 75 04  
|%.u.....u....Qu.|
00000020  25 0a 81 02 75 08 95 01  81 03 05 01 75 10 55 00  
|%...u.......u.U.|
00000030  65 00 09 30 35 00 26 00  10 46 00 10 81 02 09 31  
|e..05.&..F.....1|
00000040  26 00 10 46 00 10 81 02  c0 a1 00 05 0d 09 42 15  
|&..F..........B.|
00000050  00 25 01 75 01 95 01 81  02 75 03 81 03 09 51 75  
|.%.u.....u....Qu|
00000060  04 25 0a 81 02 75 08 95  01 81 03 05 01 75 10 55  
|.%...u.......u.U|
00000070  00 65 00 09 30 35 00 26  00 10 46 00 10 81 02 09  
|.e..05.&..F.....|
00000080  31 26 00 10 46 00 10 81  02 c0 a1 00 05 0d 09 42  
|1&..F..........B|
00000090  15 00 25 01 75 01 95 01  81 02 75 03 81 03 09 51  
|..%.u.....u....Q|
000000a0  75 04 25 0a 81 02 75 08  95 01 81 03 05 01 75 10  
|u.%...u.......u.|
000000b0  55 00 65 00 09 30 35 00  26 00 10 46 00 10 81 02  
|U.e..05.&..F....|
000000c0  09 31 26 00 10 46 00 10  81 02 c0 a1 00 05 0d 09  
|.1&..F..........|
000000d0  42 15 00 25 01 75 01 95  01 81 02 75 03 81 03 09  
|B..%.u.....u....|
000000e0  51 75 04 25 0a 81 02 75  08 95 01 81 03 05 01 75  
|Qu.%...u.......u|
000000f0  10 55 00 65 00 09 30 35  00 26 00 10 46 00 10 81  
|.U.e..05.&..F...|
00000100  02 09 31 26 00 10 46 00  10 81 02 c0 a1 00 05 0d  
|..1&..F.........|
00000110  09 42 15 00 25 01 75 01  95 01 81 02 75 03 81 03  
|.B..%.u.....u...|
00000120  09 51 75 04 25 0a 81 02  75 08 95 01 81 03 05 01  
|.Qu.%...u.......|
00000130  75 10 55 00 65 00 09 30  35 00 26 00 10 46 00 10  
|u.U.e..05.&..F..|
00000140  81 02 09 31 26 00 10 46  00 10 81 02 c0 05 0d 09  
|...1&..F........|
00000150  54 95 01 75 08 15 00 25  0a 81 02 09 55 b1 02 95  
|T..u...%....U...|
00000160  3e b1 03 c0 05 0d 09 02  a1 01 85 cc 09 20 a1 00  
|>............ ..|
00000170  09 42 09 44 09 3c 09 45  15 00 25 01 75 01 95 04  
|.B.D.<.E..%.u...|
00000180  81 02 95 01 09 32 81 02  95 03 81 03 05 01 09 30  
|.....2.........0|
00000190  75 10 95 01 a4 55 0d 65  13 35 00 26 00 10 46 00  
|u....U.e.5.&..F.|
000001a0  10 81 02 09 31 26 00 10  46 00 10 81 02 b4 05 0d  
|....1&..F.......|
000001b0  09 30 26 ff 00 81 02 75  08 09 3d 15 81 25 7f 81  
|.0&....u..=..%..|
000001c0  02 09 3e 15 81 25 7f 81  02 c0 c0 05 01 09 02 a1  
|..>..%..........|
000001d0  01 85 58 09 01 a1 00 05  09 19 01 29 02 15 00 25  
|..X........)...%|
000001e0  01 75 01 95 02 81 02 95  06 81 03 05 01 09 30 15  
|.u............0.|
000001f0  00 26 00 10 09 31 26 00  10 75 10 95 02 55 0e 65  
|.&...1&..u...U.e|
00000200  11 35 00 46 00 10 81 02  09 38 15 81 25 7f 75 08  
|.5.F.....8..%.u.|
00000210  95 01 81 06 c0 c0                                 |......|

And here is the output from lsusb -c:

Bus 003 Device 003: ID 4c4a:4155 Jieli Technology USB Composite Device
Couldn't open device, some information will be missing
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            0 [unknown]
   bDeviceSubClass         0 [unknown]
   bDeviceProtocol         0
   bMaxPacketSize0        64
   idVendor           0x4c4a Jieli Technology
   idProduct          0x4155 USB Composite Device
   bcdDevice            1.00
   iManufacturer           1 Jieli Technology
   iProduct                2 USB Composite Device
   iSerial                 3 FFFFFFFFFFFFFFFF
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength       0x0029
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xa0
       (Bus Powered)
       Remote Wakeup
     MaxPower              100mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         3 Human Interface Device
       bInterfaceSubClass      0 [unknown]
       bInterfaceProtocol      0
       iInterface              0
         HID Device Descriptor:
           bLength                 9
           bDescriptorType        33
           bcdHID               1.10
           bCountryCode           33 Unknown
           bNumDescriptors         1
           bDescriptorType        34 (null)
           wDescriptorLength     534
           Report Descriptors:
             ** UNAVAILABLE **
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x82  EP 2 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0020  1x 32 bytes
         bInterval               1

Best regards,

Staffan



> 
>> The issue is not specific to the 6.12.y series and confirmed in 6.16.3
>> as well.
>> 
>> Staffan Melin did bisect the kernels between 6.12.38 (which was still
>> working) and 6.1.41 (which was not), confirming by bisection that the
>> offending commit is
>> 
>> 1a8953f4f774 ("HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY")
>> 
>> #regzbot introduced: 1a8953f4f774
>> #regzbot monitor: https://bugs.debian.org/1114557
>> 
>> So it looks that the quirk applied is unfortunately affecting
>> negatively as well Staffan Melin case.
>> 
>> Can you have a look?
>> 
>> Regards,
>> Salvatore
>> 

  reply	other threads:[~2025-09-08  9:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 15:10 [regression] 1a8953f4f774 ("HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY") causes issue with ID 4c4a:4155 Jieli Technology USB Composite Device Salvatore Bonaccorso
2025-09-08  4:10 ` Terry Junge
2025-09-08  9:00   ` Staffan Melin [this message]
2025-09-12 12:49 ` zhangheng
2025-09-12 19:57   ` Staffan Melin
2025-09-13  8:53     ` Salvatore Bonaccorso
2025-09-13  8:55       ` Salvatore Bonaccorso
2025-09-13 13:11         ` Staffan Melin
2025-09-15  8:37           ` zhangheng
2025-09-15 23:06             ` Terry Junge
2025-09-18 14:05               ` zhangheng
2025-09-18 19:56                 ` Staffan Melin
2025-09-22  9:21                   ` zhangheng
2025-09-22 18:33                     ` Staffan Melin
2025-09-29  0:39                       ` Linux Hid

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=a96b110b6b6d9a74506f1cc27cd44b49@oscillator.se \
    --to=staffan.melin@oscillator.se \
    --cc=1114557@bugs.debian.org \
    --cc=bentiss@kernel.org \
    --cc=carnil@debian.org \
    --cc=jkosina@suse.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxhid@cosmicgizmosystems.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=zhangheng@kylinos.cn \
    /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).