linux-kernel - Re: [PATCH] USB: serial: ftdi_sio: add device ID for U-Blox EVK-M101

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aO5kBAjE6EMG2aUE@hovoldconsulting.com>
Date: Tue, 14 Oct 2025 16:53:56 +0200
From: Johan Hovold <johan@...nel.org>
To: Oleksandr Suvorov <cryosay@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: serial: ftdi_sio: add device ID for U-Blox EVK-M101

On Fri, Sep 26, 2025 at 09:02:35AM +0300, Oleksandr Suvorov wrote:
> The U-Blox 

Missing product name?

> has a USB Type-C port that presents itself as a USB device
> (1546:0506) [1] with four attached FTDI serial ports, connected to:
> - EVK-M101 current sensors
> - EVK-M101 I2C
> - EVK-M101 UART
> - EVK-M101 port D
> 
> This commit registers U-Blox's VID/PID of this device so that FTDI SIO driver
> successfully registers these 4 serial ports.

Are you sure you should not just register the UART port? Some FTDI chips
support I2C but you'd need a different driver for that.

> [1]
> usb 5-1.3: new high-speed USB device number 11 using xhci_hcd
> usb 5-1.3: New USB device found, idVendor=1546, idProduct=0506, bcdDevice= 8.00
> usb 5-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 5-1.3: Product: EVK-M101
> usb 5-1.3: Manufacturer: u-blox AG
> 
> Datasheet: https://content.u-blox.com/sites/default/files/documents/EVK-M10_UserGuide_UBX-21003949.pdf

The user guide also says "Do not use this COM port" for all ports but
the UART port.

Johan