Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753562AbdGSN3v convert rfc822-to-8bit (ORCPT ); Wed, 19 Jul 2017 09:29:51 -0400 Received: from mail-out.m-online.net ([212.18.0.10]:49513 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751825AbdGSN3t (ORCPT ); Wed, 19 Jul 2017 09:29:49 -0400 X-Auth-Info: u9M36Eaj+NhioidwVAHcOqap9i1uHGq9vsht+5X8uKM= Date: Wed, 19 Jul 2017 15:29:42 +0200 From: Anatolij Gustschin To: =?UTF-8?B?QmrDuHJu?= Mork Cc: Johan Hovold , Lee Jones , Linus Walleij , Alan Tull , Moritz Fischer , linux-gpio@vger.kernel.org, linux-fpga@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Message-ID: <20170719152942.6202fdbb@crub> In-Reply-To: <87vamy81f1.fsf@miraculix.mork.no> References: <1499374158-12388-1-git-send-email-agust@denx.de> <1499374158-12388-2-git-send-email-agust@denx.de> <87y3s0adr3.fsf@miraculix.mork.no> <20170707115329.06dcdb69@crub> <20170710123427.GJ29638@localhost> <20170711085237.4c472621@crub> <20170712085003.GQ29638@localhost> <87vamy81f1.fsf@miraculix.mork.no> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1028 Lines: 26 On Wed, 12 Jul 2017 11:11:46 +0200 Bjørn Mork bjorn@mork.no wrote: >Johan Hovold 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