All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220193] PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022
Date: Mon, 10 Aug 2026 09:47:29 +0000	[thread overview]
Message-ID: <bug-220193-208809-3XyDDA0j45@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220193-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220193

Wei Huang (huangwei@kylinos.cn) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |huangwei@kylinos.cn

--- Comment #1 from Wei Huang (huangwei@kylinos.cn) ---
Hi leStoppe,

Thanks for reporting this and bisecting the regression to commit
4cc01410e1c1.

A fix has been submitted to the linux-usb mailing list. It narrows
the OWON match from USB_DEVICE() to USB_DEVICE_AND_INTERFACE_INFO(),
requiring bInterfaceClass=0x05 (Physical Interface Device) as
reported in the HDS200 USB descriptor. This should let the VDS1022
fall back to the generic usbserial driver as before, provided it
uses a different interface class.

The patch can be found here:
https://lore.kernel.org/linux-usb/20260810091322.2201740-1-huangwei@kylinos.cn/

Could you test whether this resolves the issue on your VDS1022?
If the VDS1022 also happens to use bInterfaceClass=0x05, further
work (e.g. a probe callback checking the device string descriptor)
may be needed.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2026-08-10  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 21:09 [Bug 220193] New: PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022 bugzilla-daemon
2026-08-10  9:47 ` bugzilla-daemon [this message]
2026-08-10 19:35 ` [Bug 220193] " bugzilla-daemon

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=bug-220193-208809-3XyDDA0j45@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.