Commit 2436236e authored by Marek Vasut's avatar Marek Vasut Committed by Greg Kroah-Hartman

USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit

commit 31c5d192 upstream.

This development kit has an FT4232 on it with a custom USB VID/PID.
The FT4232 provides four UARTs, but only two are used. The UART 0
is used by the FlashPro5 programmer and UART 2 is connected to the
SmartFusion2 CortexM3 SoC UART port.

Note that the USB VID is registered to Actel according to Linux USB
VID database, but that was acquired by Microsemi.
Signed-off-by: default avatarMarek Vasut <marex@denx.de>
Signed-off-by: default avatarJohan Hovold <johan@kernel.org>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent f34b103c
...@@ -873,6 +873,7 @@ static const struct usb_device_id id_table_combined[] = { ...@@ -873,6 +873,7 @@ static const struct usb_device_id id_table_combined[] = {
{ USB_DEVICE_AND_INTERFACE_INFO(MICROCHIP_VID, MICROCHIP_USB_BOARD_PID, { USB_DEVICE_AND_INTERFACE_INFO(MICROCHIP_VID, MICROCHIP_USB_BOARD_PID,
USB_CLASS_VENDOR_SPEC, USB_CLASS_VENDOR_SPEC,
USB_SUBCLASS_VENDOR_SPEC, 0x00) }, USB_SUBCLASS_VENDOR_SPEC, 0x00) },
{ USB_DEVICE_INTERFACE_NUMBER(ACTEL_VID, MICROSEMI_ARROW_SF2PLUS_BOARD_PID, 2) },
{ USB_DEVICE(JETI_VID, JETI_SPC1201_PID) }, { USB_DEVICE(JETI_VID, JETI_SPC1201_PID) },
{ USB_DEVICE(MARVELL_VID, MARVELL_SHEEVAPLUG_PID), { USB_DEVICE(MARVELL_VID, MARVELL_SHEEVAPLUG_PID),
.driver_info = (kernel_ulong_t)&ftdi_jtag_quirk }, .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk },
......
...@@ -873,6 +873,12 @@ ...@@ -873,6 +873,12 @@
#define FIC_VID 0x1457 #define FIC_VID 0x1457
#define FIC_NEO1973_DEBUG_PID 0x5118 #define FIC_NEO1973_DEBUG_PID 0x5118
/*
* Actel / Microsemi
*/
#define ACTEL_VID 0x1514
#define MICROSEMI_ARROW_SF2PLUS_BOARD_PID 0x2008
/* Olimex */ /* Olimex */
#define OLIMEX_VID 0x15BA #define OLIMEX_VID 0x15BA
#define OLIMEX_ARM_USB_OCD_PID 0x0003 #define OLIMEX_ARM_USB_OCD_PID 0x0003
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment