All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "michael.lee@omron.com" <michael.lee@omron.com>
Cc: Chris Ruehl <chris.ruehl@gtsys.com.hk>,
	Lars Melin <larsm17@gmail.com>,
	USB list <linux-usb@vger.kernel.org>,
	Oliver Neukum <oneukum@suse.com>
Subject: Re: serial: usb: cdc-acm: OMRON B5L ToF, device probe failed
Date: Tue, 21 Jun 2022 09:16:44 +0200	[thread overview]
Message-ID: <YrFwXPUF9RfzTWzk@kroah.com> (raw)
In-Reply-To: <OSZP286MB1776CCBCBFE38B25C7DB9978E1B39@OSZP286MB1776.JPNP286.PROD.OUTLOOK.COM>

On Tue, Jun 21, 2022 at 12:38:22AM +0000, michael.lee@omron.com wrote:
> Dear Chris,
> 
> The below is the reply from Japan.
> 
> Dose they do the below commnad after connect B5L to USB?
> 
> sudo modprobe usbserial vendor=0x0590 product=0x00ca

So that means this is just a "generic" usb-serial device, not a cdc-acm
one at all.  Just add the device id to the generic usb-serial driver and
you should be fine.

BUT, that implies that the interrupt endpoints are useless?  Why are
they there?  How is flow control handled in this device?

Perhaps ask what the chip is in the device, that might help out here
more.

thanks,

greg k-h

  reply	other threads:[~2022-06-21  7:16 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 [this message]
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
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=YrFwXPUF9RfzTWzk@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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.