Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices

From	Anatolij Gustschin <agust@denx.de>
Newsgroups	linux.kernel
Subject	Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices
Date	2017-07-19 15:30 +0200
Message-ID	<u4Xd8-Hy-3@gated-at.bofh.it> (permalink)
References	(3 earlier) <u0ydj-2cj-3@gated-at.bofh.it> <u1G8O-53s-33@gated-at.bofh.it> <u1Xjk-7kC-3@gated-at.bofh.it> <u2lEZ-5ZJ-3@gated-at.bofh.it> <u2lYl-6m0-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, 12 Jul 2017 11:11:46 +0200
Bjørn Mork bjorn@mork.no wrote:

>Johan Hovold <johan@kernel.org> writes:
>> On Tue, Jul 11, 2017 at 08:52:37AM +0200, Anatolij Gustschin wrote:
>>  
>>> For devices with connected EEPROM some modes (including UART) are
>>> configurable in the EEPROM. For devices without EEPROM the default
>>> mode is always UART, but FIFO-, Bitbang- and MPSSE-mode can be
>>> switched via commands to the the chip.  
>>
>> IIRC we should be able read from the EEPROM, and I would at least expect
>> there to be a way to retrieve the current mode as well.  
>
>Stupid question, I know, but I cannot help thinking: If you have an
>EEPROM then why the h... don't you use an application specific device
>ID?

It would make sense for adapter devices that you can buy and plug.
In my particular case the configuration device with FTDI chips is
internal part of embedded board, the configuration interface is
never exposed to end users. I doesn't make sense to register an
ID for such hardware.

Thanks,
Anatolij

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Anatolij Gustschin <agust@denx.de> - 2017-07-19 15:30 +0200
  RE: [PATCH 1/3] mfd: Add support for FTDI FT232H devices David Laight <David.Laight@ACULAB.COM> - 2017-07-19 15:40 +0200
    Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Anatolij Gustschin <agust@denx.de> - 2017-07-19 17:10 +0200

csiph-web