From: Johan Hovold <johan@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: stable@vger.kernel.org, Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
Date: Mon, 13 Feb 2017 10:29:14 +0100 [thread overview]
Message-ID: <20170213092914.GA26299@localhost> (raw)
In-Reply-To: <20170210161612.26465-1-marex@denx.de>
[+CC: linux-usb]
Always make sure to CC linux-usb for USB patches.
On Fri, Feb 10, 2017 at 05:16:12PM +0100, Marek Vasut wrote:
> 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.
Don't you want to use the "jtag" quirk for this one then to prevent the
driver from binding to interface 0? Or do you still need this interface
to be accessible as a tty device?
> Note that the USB VID is registered to Actel according to Linux USB
> VID database, but that was acquired by Microsemi.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: stable <stable@vger.kernel.org>
> Cc: Johan Hovold <johan@kernel.org>
> ---
> drivers/usb/serial/ftdi_sio.c | 1 +
> drivers/usb/serial/ftdi_sio_ids.h | 10 ++++++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> index c98cf10be5af..14f0fb34f655 100644
> --- a/drivers/usb/serial/ftdi_sio.c
> +++ b/drivers/usb/serial/ftdi_sio.c
> @@ -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_CLASS_VENDOR_SPEC,
> USB_SUBCLASS_VENDOR_SPEC, 0x00) },
> + { USB_DEVICE(ACTEL_VID, MICROSEMI_ARROW_SF2PLUS_BOARD_PID) },
> { USB_DEVICE(JETI_VID, JETI_SPC1201_PID) },
> { USB_DEVICE(MARVELL_VID, MARVELL_SHEEVAPLUG_PID),
> .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk },
> diff --git a/drivers/usb/serial/ftdi_sio_ids.h b/drivers/usb/serial/ftdi_sio_ids.h
> index 168ccb03ce08..a9d538d18344 100644
> --- a/drivers/usb/serial/ftdi_sio_ids.h
> +++ b/drivers/usb/serial/ftdi_sio_ids.h
> @@ -627,6 +627,16 @@
> #define MICROCHIP_USB_BOARD_PID 0x000A /* CDC RS-232 Emulation Demo */
>
> /*
> + * Microsemi/Arrow SF2PLUS Dev Kit
> + *
> + * This board has an FT4232 on it which provides four UART ports.
> + * UART 0 is used by the FlashPro5 programmer, UART 2 is connected
> + * to the UART of an CortexM3 SoC-FPGA on the board.
> + */
> +#define ACTEL_VID 0x1514
> +#define MICROSEMI_ARROW_SF2PLUS_BOARD_PID 0x2008
> +
Please place this before the Olimex section to try to maintain some
order based on VID.
> +/*
> * RATOC REX-USB60F
> */
> #define RATOC_VENDOR_ID 0x0584
Thanks,
Johan
next prev parent reply other threads:[~2017-02-13 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 16:16 [PATCH] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit Marek Vasut
2017-02-13 9:29 ` Johan Hovold [this message]
2017-02-14 4:21 ` Marek Vasut
2017-04-17 11:59 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2017-04-18 18:07 Marek Vasut
2017-04-19 8:00 ` Johan Hovold
2017-04-19 8:31 ` Marek Vasut
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=20170213092914.GA26299@localhost \
--to=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marex@denx.de \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.