Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754851AbdGLJL6 (ORCPT ); Wed, 12 Jul 2017 05:11:58 -0400 Received: from canardo.mork.no ([148.122.252.1]:50459 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750738AbdGLJLz (ORCPT ); Wed, 12 Jul 2017 05:11:55 -0400 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: Johan Hovold Cc: Anatolij Gustschin , 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 Organization: m 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> Date: Wed, 12 Jul 2017 11:11:46 +0200 In-Reply-To: <20170712085003.GQ29638@localhost> (Johan Hovold's message of "Wed, 12 Jul 2017 10:50:03 +0200") Message-ID: <87vamy81f1.fsf@miraculix.mork.no> User-Agent: Gnus/5.130015 (Ma Gnus v0.15) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v6C9C9D2017153 Content-Length: 646 Lines: 17 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? Bjørn