public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: Johan Hovold <johan@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is enabled
Date: Tue, 25 Jul 2017 13:43:54 +0200	[thread overview]
Message-ID: <20170725114354.GM2729@localhost> (raw)
In-Reply-To: <20170719132327.2ddb8fbe@crub>

On Wed, Jul 19, 2017 at 01:23:27PM +0200, Anatolij Gustschin wrote:
> On Wed, 19 Jul 2017 11:03:11 +0200
> Johan Hovold johan@kernel.org wrote:
> 
> >On Thu, Jul 13, 2017 at 06:25:25PM +0200, Anatolij Gustschin wrote:
> >> On FT232H the interface mode can be configured in the EEPROM,
> >> and the async UART mode is configured by default. The chip is
> >> also in async UART mode if no EEPROM is connected.
> >> 
> >> Check the EEPROM configuration and do not bind as serial device
> >> when different interface mode is programmed in the EEPROM.  
> >
> >Thanks for the patch. As you may have inferred from my reply to your MFD
> >series, this won't be needed for a while still however.
> >
> >Also note that some people already use asynchronous FIFO mode using this
> >driver (also mentioned in the datasheets as an option) so only binding
> >in UART mode would be too restrictive.
> 
> You probably mean asynchronous bitbang mode, not asynchronous FIFO
> mode?

No, I really meant asynchronous FIFO mode. And as mentioned in the data
sheets that can be used with the normal serial (VCP) drivers on both
Linux and that other OS.

> This bitbang mode can always be set by sending a chip command
> (mentioned as software configured in the datasheets)
> Could you please point to code in this driver used for non-UART modes?
> I don't see such code by a quick glance. There are some quirks for
> various JTAG adapters to skip binding as serial port (the ftdi_sio
> driver is not used in JTAG operation modes then). Or do people use
> usual serial interface to send data in bitbang modes?

Exactly.

> Async and sync FIFO (FT245) modes however can only be configured via
> EEPROM settings, at least for FT232H.

Right.

Thanks,
Johan

      reply	other threads:[~2017-07-25 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 16:25 [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is enabled Anatolij Gustschin
2017-07-19  9:03 ` Johan Hovold
2017-07-19 11:23   ` Anatolij Gustschin
2017-07-25 11:43     ` Johan Hovold [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=20170725114354.GM2729@localhost \
    --to=johan@kernel.org \
    --cc=agust@denx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.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