Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753997AbdGSNju (ORCPT ); Wed, 19 Jul 2017 09:39:50 -0400 Received: from smtp-out4.electric.net ([192.162.216.195]:55872 "EHLO smtp-out4.electric.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753408AbdGSNjq (ORCPT ); Wed, 19 Jul 2017 09:39:46 -0400 From: David Laight To: "'Anatolij Gustschin'" , =?utf-8?B?QmrDuHJuIE1vcms=?= 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 Thread-Topic: [PATCH 1/3] mfd: Add support for FTDI FT232H devices Thread-Index: AQHTAJMUvQm0lgsbrUKZbC4K1B7ObKJbJ2Jw Date: Wed, 19 Jul 2017 13:39:36 +0000 Message-ID: <063D6719AE5E284EB5DD2968C1650D6DD003C702@AcuExch.aculab.com> 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> <20170719152942.6202fdbb@crub> In-Reply-To: <20170719152942.6202fdbb@crub> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.202.99.200] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-Outbound-IP: 156.67.243.126 X-Env-From: David.Laight@ACULAB.COM X-Proto: esmtps X-Revdns: X-HELO: AcuExch.aculab.com X-TLS: TLSv1:AES128-SHA:128 X-Authenticated_ID: X-PolicySMART: 3396946, 3397078 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 base64 to 8bit by nfs id v6JDdwMY030857 Content-Length: 625 Lines: 18 From: Anatolij Gustschin > Sent: 19 July 2017 14:30 ... > >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. Sounds like you should absolutely be registering an ID so that nothing can try to use it using the default one. David