linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Messer <andi@bastelmap.de>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] Support FlashPro5 serial ports
Date: Fri, 31 Oct 2025 18:45:46 +0100	[thread overview]
Message-ID: <aQT1ynWbVTb7J2hl@zeus.ad.home.arpa> (raw)
In-Reply-To: <aQS8RwAeqjueoVXb@hovoldconsulting.com>

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

Am Fri, Oct 31, 2025 at 02:40:23PM +0100 schrieb Johan Hovold:
> On Thu, Oct 30, 2025 at 10:49:22PM +0100, Andreas Messer wrote:
> 
> > I have added more entries to the device list to make all UART Channels
> > working with my board. However it will make these UARTS show up with SF2+
> > Board too. I found at least four different device which have the 
> > same Vendor/Product ID, but I assume there are more:
> > 
> > - Trenz SMF2000: FT2232H
> >   Channel A -> JTAG, Channel B -> UART
> > 
> > - Microchip Polarfire Discovery Kit: FT4232H
> >   Channel A -> JTAG, Channel B/C/D -> UART
> 
> Where did you find these two? Do you have access to the devices?

For the Trenz I found the information in the web here:

https://wiki.trenz-electronic.de/display/PD/TEM0001+TRM

I own the Discovery Kit but the schematic is also public 
available here:

https://ww1.microchip.com/downloads/aemDocuments/documents/FPGA/ProductDocuments/BoardDesignFiles/PolarFire_SoC_Discovery_Kit_Schematics.zip


> > - Microsemi/Microchip FlashPro5: FT4232H
> >   Channel A -> JTAG
> 
> I guess you forgot "Channel B/C/D -> UART" here?

No, the standalone FlashPro5 hardware has only a JTAG Port

https://www.microchip.com/en-us/development-tool/flashpro5


> It would be good to avoid enabling unused ports on devices that only
> have one UART (e.g. to avoid regressing udev rules).
> 
> You could use something like ftdi_8u2232c_probe() and only enable the
> other ports (i.e. B and D) after comparing the product name to a
> whitelist.

Ok, I'll have a look at it and try to come with a solution. 
Thanks for the pointer!

Andreas

-- 
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2025-10-31 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 21:49 [PATCH] Support FlashPro5 serial ports Andreas Messer
2025-10-31 13:40 ` Johan Hovold
2025-10-31 17:45   ` Andreas Messer [this message]

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=aQT1ynWbVTb7J2hl@zeus.ad.home.arpa \
    --to=andi@bastelmap.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-usb@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 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).