All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Oliver Neukum <oneukum@suse.com>,
	"michael.lee@omron.com" <michael.lee@omron.com>,
	Lars Melin <larsm17@gmail.com>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: serial: usb: cdc-acm: OMRON B5L ToF, device probe failed
Date: Sat, 25 Jun 2022 10:42:37 +0800	[thread overview]
Message-ID: <00b699c1-ac40-7309-5b24-e527af999de2@gtsys.com.hk> (raw)
In-Reply-To: <85ff1357-5a70-3ee1-4098-08401f522c7a@gtsys.com.hk>



On 25/6/2022 10:35 am, Chris Ruehl wrote:
>
> On 23/6/2022 5:39 pm, Oliver Neukum wrote:
>>
>> On 23.06.22 10:55, Chris Ruehl wrote:
>>>
>>> On 23/6/2022 4:44 pm, Chris Ruehl wrote:
>>>> On 23/6/2022 4:28 pm, Oliver Neukum wrote:
>>>>> if you absolutely want it to be driven from CDC-ACM, try this
>>>>> new attached patch.
>>>>> In your original patch you used NO_UNION_NORMAL. That will allow
>>>>> a device to work without a union descriptor but with the normal
>>>>> two interfaces. This devices has what in terms of ACM is a collapsed
>>>>> interface without a union descriptor.
>>>>> The driver provides for that but then it checks for the exact
>>>>> number of required endpoints, which is three. Your device has
>>>>> four endpoints.
>>>>> The patch ignores a fourth endpoint.
>>> Apply the patch ,
>>> still no /dev/ttyACM0 comes up.
>> Hi,
>>
>> please send me dmesg. This should not happen.
>>
>>     Regards
>>         Oliver
>>
> Hi,
> sorry for let you wait but I had a bunch of testing with the b5l to deliver
> my solution to the team.
>
> here the dmesg after apply your patch & NO_NORMAL_UNION
>
> [266005.246312] usb 2-1.4.4.1: new high-speed USB device number 19 using ehci-pci
> [266005.344658] usb 2-1.4.4.1: New USB device found, idVendor=0590, 
> idProduct=00ca, bcdDevice= 2.00
> [266005.344666] usb 2-1.4.4.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [266005.344670] usb 2-1.4.4.1: Product: OMRON B5L-001011
> [266005.344673] usb 2-1.4.4.1: Manufacturer: OMRON Corporation
> [266005.344675] usb 2-1.4.4.1: SerialNumber: 010000319A1
> [266005.458809] usbcore: registered new interface driver cdc_acm
> [266005.458814] cdc_acm: USB Abstract Control Model driver for USB modems and 
> ISDN adapters
>
> T:  Bus=02 Lev=04 Prnt=05 Port=00 Cnt=01 Dev#= 19 Spd=480  MxCh= 0
> D:  Ver= 2.00 Cls=02(comm.) Sub=02 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=0590 ProdID=00ca Rev= 2.00
> S:  Manufacturer=OMRON Corporation
> S:  Product=OMRON B5L-001011
> S:  SerialNumber=010000319A1
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=  4mA
> I:* If#= 0 Alt= 0 #EPs= 4 Cls=02(comm.) Sub=02 Prot=00 Driver=(none)
> E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=03(O) Atr=03(Int.) MxPS=  64 Ivl=4096ms
> E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=4096ms
>
> -Chris
>

The Arduino and the I/O of 3 channels with a working interface to compare.

T:  Bus=02 Lev=03 Prnt=04 Port=01 Cnt=02 Dev#= 20 Spd=12   MxCh= 0
D:  Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=2341 ProdID=0042 Rev= 0.01
S:  Manufacturer=Arduino (www.arduino.cc)
S:  SerialNumber=850363135303517102C0
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=cdc_acm
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
E:  Ad=04(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms



-- 
GTSYS Limited RFID Technology
9/F, Unit E, R07, Kwai Shing Industrial Building Phase 2,
42-46 Tai Lin Pai Road, Kwai Chung, N.T., Hong Kong
Tel (852) 9079 9521

Disclaimer: https://www.gtsys.com.hk/email/classified.html


  reply	other threads:[~2022-06-25  2:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  4:11 serial: usb: cdc-acm: OMRON B5L ToF, device probe failed Chris Ruehl
2022-06-20  2:44 ` Chris Ruehl
2022-06-20  3:35   ` Lars Melin
2022-06-20  6:20     ` Chris Ruehl
2022-06-21  0:38       ` michael.lee
2022-06-21  7:16         ` Greg KH
2022-06-21 10:09         ` Oliver Neukum
2022-06-21 10:44           ` Chris Ruehl
2022-06-23  2:26           ` Chris Ruehl
2022-06-23  8:28             ` Oliver Neukum
2022-06-23  8:44               ` Chris Ruehl
2022-06-23  8:55                 ` Chris Ruehl
2022-06-23  9:39                   ` Oliver Neukum
2022-06-25  2:35                     ` Chris Ruehl
2022-06-25  2:42                       ` Chris Ruehl [this message]
2022-06-25  7:32                       ` Greg KH
2022-06-25  7:46                         ` Chris Ruehl
2022-07-20 11:12                   ` Oliver Neukum
2022-07-20 16:24     ` Oliver Neukum
  -- strict thread matches above, loose matches on Subject: below --
2022-06-15  7:25 Chris Ruehl

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=00b699c1-ac40-7309-5b24-e527af999de2@gtsys.com.hk \
    --to=chris.ruehl@gtsys.com.hk \
    --cc=larsm17@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.lee@omron.com \
    --cc=oneukum@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.