Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965155AbbEMNrF (ORCPT ); Wed, 13 May 2015 09:47:05 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:35431 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752285AbbEMNrA (ORCPT ); Wed, 13 May 2015 09:47:00 -0400 Message-ID: <555355C1.9090907@roeck-us.net> Date: Wed, 13 May 2015 06:46:41 -0700 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: 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 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> In-Reply-To: <20150513133741.GY3338@piout.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=0.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1528 Lines: 38 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. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/