From: Johan Hovold <johan@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-usb@vger.kernel.org, stable <stable@vger.kernel.org>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
Date: Wed, 19 Apr 2017 10:00:45 +0200 [thread overview]
Message-ID: <20170419080045.GD2823@localhost> (raw)
In-Reply-To: <20170418180756.29671-1-marex@denx.de>
On Tue, Apr 18, 2017 at 08:07:56PM +0200, 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.
>
> 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: usb <linux-usb@vger.kernel.org>
> Cc: Johan Hovold <johan@kernel.org>
> ---
> V2: - Move the ID in ftdi_sio_ids.h to keep it sorted by VIDs
> - Use the JTAG quirk to avoid binding channel 0, this is needed by
> the Libero software, otherwise it cannot use the programmer.
> V3: - Remove the verbose comment
> - Use USB_DEVICE_INTERFACE_NUMBER() instead of the JTAG quirk
Applied for -next, thanks.
Johan
next prev parent reply other threads:[~2017-04-19 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 18:07 [PATCH] USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit Marek Vasut
2017-04-19 8:00 ` Johan Hovold [this message]
2017-04-19 8:31 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2017-02-10 16:16 Marek Vasut
2017-02-13 9:29 ` Johan Hovold
2017-02-14 4:21 ` Marek Vasut
2017-04-17 11:59 ` 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=20170419080045.GD2823@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.