From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965381AbbEMO4Q (ORCPT ); Wed, 13 May 2015 10:56:16 -0400 Received: from mail1.bemta5.messagelabs.com ([195.245.231.140]:11885 "EHLO mail1.bemta5.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933788AbbEMO4N convert rfc822-to-8bit (ORCPT ); Wed, 13 May 2015 10:56:13 -0400 X-Env-Sender: stwiss.opensource@diasemi.com X-Msg-Ref: server-6.tower-180.messagelabs.com!1431528965!36582976!1 X-Originating-IP: [94.185.165.51] X-StarScan-Received: X-StarScan-Version: 6.13.14; banners=-,-,- X-VirusChecked: Checked From: "Opensource [Steve Twiss]" To: Guenter Roeck , Alexandre Belloni CC: "Opensource [Steve Twiss]" , "Alessandro Zummo" , LINUXKERNEL , RTCLINUX , DEVICETREE , David Dajun Chen , Dmitry Torokhov , Ian Campbell , Kumar Gala , LINUXINPUT , LINUXWATCHDOG , Lee Jones , "Liam Girdwood" , Mark Brown , Mark Rutland , Pawel Moll , Rob Herring , Samuel Ortiz , "Support Opensource" , Wim Van Sebroeck Subject: RE: [rtc-linux] [PATCH V1 3/6] rtc: da9062: DA9062 RTC driver Thread-Topic: [rtc-linux] [PATCH V1 3/6] rtc: da9062: DA9062 RTC driver Thread-Index: AQHQeRyE3tWAwMSBREa6qYm2Bfc80p11DMkAgAG2NlCAAzMqAIAAAaGAgAAJMYCAAAKDgIAAF3tA Date: Wed, 13 May 2015 14:56:04 +0000 Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B22A465@SW-EX-MBX02.diasemi.com> References: <860a3b6dc7f8dac95c0e36967f24551af8805f7b.1429280614.git.stwiss.opensource@diasemi.com> <20150510095838.GF3338@piout.net> <6ED8E3B22081A4459DAC7699F3695FB7014B22A3F3@SW-EX-MBX02.diasemi.com> <20150513125858.GX3338@piout.net> <55534BEF.7020409@roeck-us.net> <20150513133741.GY3338@piout.net> <555355C1.9090907@roeck-us.net> In-Reply-To: <555355C1.9090907@roeck-us.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.26.77] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guenter & Alexandre, On 13 May 2015 14:47 Guenter Roeck wrote: > On 05/13/2015 06:37 AM, Alexandre Belloni wrote: > > On 13/05/2015 at 06:04:47 -0700, Guenter Roeck wrote : > >> Don't know how this is handled for rtc drivers, but in other subsystems > >> we just live with the original name. I don't see a need to rename a driver > >> just because it starts supporting more hardware, and xxx is weird anyway > >> since it suggests everything from 000 to 999, which is much worse than > >> just sticking with 9063. > >> > > > > Yes, in particular if at some point in time a new IP matching those xxx > > is completely different from the previous one. I'm not fond of renaming > > the driver either but if diasemi thinks that what they want, I'm open to > > let it happen. But clearly, I don't want to end up in a situation like > > the tlv320aic where you don't know which driver correspond to which > > chip: > > > > sound/soc/codecs/tlv320aic31xx.c > > sound/soc/codecs/tlv320aic31xx.h > > sound/soc/codecs/tlv320aic32x4.c > > sound/soc/codecs/tlv320aic32x4.h > > sound/soc/codecs/tlv320aic3x.c > > sound/soc/codecs/tlv320aic3x.h > > sound/soc/codecs/tlv320dac33.c > > sound/soc/codecs/tlv320dac33.h > > > > Go figure that the tlv320aic3104 can be supported by both tlv320aic3x.c > > and tlv320aic32x4.c but not tlv320aic31xx.c... > > > > Unfortunately that is exactly what is going to happen. Thanks for this clarification. We'll follow your advice and keep the name as da9063 Regards, Steve