Re: [PATCH] USB: serial: simple: narrow OWON match to avoid breaking VDS1022

[Huang Wei <huangwei@kylinos.cn>]

On Mon, Aug 10, 2026 at 07:43:33PM +0200, Greg Kroah-Hartman wrote:
> Where is the "owon driver" located at? Is it just a userspace program
> or a real kernel driver?

Sorry for the unclear wording. The "owon driver" refers to the
owon_device usb_serial_driver registered in
drivers/usb/serial/usb-serial-simple.c. It is a real kernel driver,
added by the same commit 4cc01410e1c1 that introduced the regression.
I'll reword the commit message to avoid the ambiguity if a v2 is
needed.

> thanks,
> greg k-h

To address Michal's point: the VDS1022 community indeed has a libusb
based userspace tool [1], which needs direct USB access. Before commit
4cc01410e1c1, the owon driver did not exist and the device was not
claimed by any specific kernel driver. After that commit, the broad
USB_DEVICE() match caused the owon driver to claim the VDS1022 as
well, preventing the userspace tool from accessing it.

This patch restores the pre-regression behavior by narrowing the
match to the HDS200's interface class (0x05). The reporter has
confirmed that the VDS1022 now falls back to the generic usbserial
driver and works again [2].

[1] https://github.com/florentbr/OWON-VDS1022
[2] https://lore.kernel.org/linux-usb/20260810091322.2201740-1-huangwei@kylinos.cn/

As for the broader kernel-vs-libusb conflict Michal raised, it is
valid but predates this regression and is outside the scope of this
fix. The generic usbserial driver can be prevented from claiming the
device at the user's discretion (e.g. via unbinding or a udev rule)
if direct libusb access is needed.

Best regards,
Huang Wei