public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: "Ng, Boon Khai" <boon.khai.ng@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb <linux-usb@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Boon Khai Ng <boon.khai.ng@altera.com>,
	Tien Sung Ang <tien.sung.ang@altera.com>
Subject: Re: [PATCH v2] USB: serial: ftdi_sio: add support for Altera USB Blaster 3
Date: Tue, 11 Mar 2025 13:33:21 +0100	[thread overview]
Message-ID: <Z9AtkeGJqFTGMyTB@hovoldconsulting.com> (raw)
In-Reply-To: <DM8PR11MB5751B33EF33ED26FD8E63508C1D12@DM8PR11MB5751.namprd11.prod.outlook.com>

On Tue, Mar 11, 2025 at 10:34:33AM +0000, Ng, Boon Khai wrote:

> > These configurations were not mentioned in the commit message. Are they
> > also used for embedded designs?
> 
> Looks like the table I provided in the commit message is mismatched with 
> the one that I intended to check in for upstream.
> 
> Let me correct this, the one that I published for upstream was the actual tested
> code, whereby we want the UART to be exposed to the ftdi_sio driver.
> 
> Below is the updated table, 
> 1) PID 0x6022, FT2232, 1 JTAG port(Port A) + Port B as UART
> 2) PID 0x6025, FT4232, 1 JTAG port(Port A) + Port C as UART
> 3) PID 0x6026, FT4232, 1 JTAG port(Port A) + Port C, D as UART
> 4) PID 0x6029, FT4232, 1 JTAG port(Port B) + Port C as UART
> 5) PID 0x602a, FT4232, 1 JTAG port(Port B) + Port C, D as UART
> 6) PID 0x602c, FT4232, 1 JTAG port(Port A) + Port B as UART
> 7) PID 0x602d, FT4232, 1 JTAG port(Port A) + Port B, C as UART
> 8) PID 0x602e, FT4232, 1 JTAG port(Port A) + Port B, C, D as UART
> 
> Since we need UART to be exposed to the ftdi_sio driver and the cable USB Blaster
> does not support UART, will reword that on the commit message to remove the 
> cable USB Blaster and left only the on-board USB Blaster.

It may still be good to mention the cable in some way as it's not
obvious that there are both standalone (cable) and embedded variants.
 
> Will submit a v3 on this, with the reworded commit message plus the change log.

Sounds good. I'll wait for the v3.

Johan

  reply	other threads:[~2025-03-11 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 15:43 [PATCH v2] USB: serial: ftdi_sio: add support for Altera USB Blaster 3 Boon Khai Ng
2025-03-11  7:58 ` Johan Hovold
2025-03-11 10:34   ` Ng, Boon Khai
2025-03-11 12:33     ` Johan Hovold [this message]
2025-03-11 13:12       ` Ng, Boon Khai

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=Z9AtkeGJqFTGMyTB@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=boon.khai.ng@altera.com \
    --cc=boon.khai.ng@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tien.sung.ang@altera.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