From: Johan Hovold <johan@kernel.org>
To: Vasyl Vavrychuk <vvavrychuk@gmail.com>
Cc: linux-usb@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: USB: ftdi_sio: Use jtag quirk for Arrow USB Blaster
Date: Mon, 16 Apr 2018 09:33:35 +0200 [thread overview]
Message-ID: <20180416073335.GL10795@localhost> (raw)
On Wed, Apr 11, 2018 at 05:05:13PM +0300, Vasyl Vavrychuk wrote:
> Arrow USB Blaster integrated on MAX1000 board uses the same vendor ID
> (0x0403) and product ID (0x6010) as the "original" FTDI device.
>
> This patch avoids picking up by ftdi_sio of the first interface of this
> USB device. After that this device can be used by Arrow user-space JTAG
> driver.
>
> Signed-off-by: Vasyl Vavrychuk <vvavrychuk@gmail.com>
> ---
> drivers/usb/serial/ftdi_sio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> index 87202ad5a50d..3bab6f83f6de 100644
> --- a/drivers/usb/serial/ftdi_sio.c
> +++ b/drivers/usb/serial/ftdi_sio.c
> @@ -1899,7 +1899,8 @@ static int ftdi_8u2232c_probe(struct usb_serial *serial)
>
> if (udev->product &&
> (!strcmp(udev->product, "BeagleBone/XDS100V2") ||
> - !strcmp(udev->product, "SNAP Connect E10")))
> + !strcmp(udev->product, "SNAP Connect E10") ||
> + !strcmp(udev->product, "Arrow USB Blaster")))
I reordered these alphabetically before applying.
Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-16 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 7:33 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 14:05 USB: ftdi_sio: Use jtag quirk for Arrow USB Blaster Vasyl Vavrychuk
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=20180416073335.GL10795@localhost \
--to=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vvavrychuk@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).