Linux USB
 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: Thu, 19 Nov 2026 02:04:53 +0000	[thread overview]
Message-ID: <bug-220193-208809-Zf1q1xbCtg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220193-208809@https.bugzilla.kernel.org/>

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

--- Comment #10 from Wei Huang (daway320@163.com) ---
Hi leStoppe,

Closing the loop here: the USB serial maintainer has weighed in on
the mailing list thread.

Johan's take: there are now users of the in-kernel owon driver (the
HDS200 serial use case the original patch was written for), and
libusb itself has a mechanism to unbind a kernel driver when a
userspace application wants the device. So the preference is to keep
the broad match as is, and VDS1022 users should unbind the driver
from userspace rather than have the kernel match narrowed.

The v2 patch has accordingly been withdrawn - nothing will change in
the kernel for this device.

What this means for you in practice: your current workaround (module
blacklist) is the way the maintainer expects this to be handled.
The options:

1. Module blacklist (what you already do):

       blacklist usb-serial-simple

   Note this also disables the simple driver's other devices
   (NovAtel GPS etc.) - fine if you have none of those.

2. udev unbind rule (finer-grained; untested on my side, please
   treat as a starting point):

       ACTION=="add", SUBSYSTEM=="usb", DEVTYPE=="usb_interface",
DRIVERS=="owon", ATTRS{idVendor}=="5345", ATTRS{idProduct}=="1234",
RUN{program}="/bin/sh -c 'echo %k > /sys/bus/usb/drivers/owon/unbind'"

Since the OWON software you use does not call the libusb detach
interface, the unbind needs to happen at the system level as above
(or upstream in that tool).

Sorry it did not land as a kernel fix in the end, but thanks again
for the thorough report - your descriptor dump settled the technical
questions, and the maintainer's decision was explicitly informed by
the real-world usage data from this bug.

Reference thread:
https://lore.kernel.org/linux-usb/20260810091322.2201740-1-huangwei@kylinos.cn/

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

      parent reply	other threads:[~2026-11-19  2:04 UTC|newest]

Thread overview: 11+ 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 ` [Bug 220193] " bugzilla-daemon
2026-08-10 19:35 ` bugzilla-daemon
2026-08-11 13:24 ` bugzilla-daemon
2026-08-26  2:50 ` bugzilla-daemon
2026-10-12  8:18 ` bugzilla-daemon
2026-10-13 21:28 ` bugzilla-daemon
2026-10-15  3:02 ` bugzilla-daemon
2026-10-30 21:19 ` bugzilla-daemon
2026-11-03  3:27 ` bugzilla-daemon
2026-11-19  2:04 ` bugzilla-daemon [this message]

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-Zf1q1xbCtg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox