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

[Oleksandr Suvorov]

Hi Johan,

On Wed, Oct 15 2025 at 16:36 Johan Hovold <johan@xxxxxxxxxx> wrote:
>
> On Fri, Sep 26, 2025 at 09:02:35AM +0300, Oleksandr Suvorov wrote:
> > The U-Blox
>
> Missing product name?

Thanks, I'll fix it.

> > 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.

Thanks for pointing this out, looks like I should add a custom probe()
for this device.
Preparing v2.

> > [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.

Yes, you're right, thanks. It's just not that easy hacking the kernel
while defending from russian invaders :)

> Johan

-- 
Best regards
Oleksandr, sr.soldier in the Armed Forces of Ukraine