Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1691144 > unrolled thread

Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is enabled

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is  enabled Johan Hovold <johan@kernel.org> - 2017-07-19 11:10 +0200
    Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is  enabled Anatolij Gustschin <agust@denx.de> - 2017-07-19 13:30 +0200
      Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is  enabled Johan Hovold <johan@kernel.org> - 2017-07-25 13:50 +0200

#1691144 — Re: [PATCH] USB: serial: ftdi_sio: only bind FT232H if UART mode is enabled

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.

Thanks,
Johan

[toc] | [next] | [standalone]

#1691529

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? 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?

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

Thanks,
Anatolij

[toc] | [prev] | [next] | [standalone]

#1695640

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web