Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934457AbbEMMbs (ORCPT ); Wed, 13 May 2015 08:31:48 -0400 Received: from mail1.bemta5.messagelabs.com ([195.245.231.149]:32849 "EHLO mail1.bemta5.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933650AbbEMMbm convert rfc822-to-8bit (ORCPT ); Wed, 13 May 2015 08:31:42 -0400 X-Env-Sender: stwiss.opensource@diasemi.com X-Msg-Ref: server-9.tower-178.messagelabs.com!1431520298!37121226!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: Alexandre Belloni CC: 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: AQHQeRyE3tWAwMSBREa6qYm2Bfc80p11DMkAgAG2NlA= Date: Wed, 13 May 2015 12:31:36 +0000 Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B22A3F3@SW-EX-MBX02.diasemi.com> References: <860a3b6dc7f8dac95c0e36967f24551af8805f7b.1429280614.git.stwiss.opensource@diasemi.com> <20150510095838.GF3338@piout.net> In-Reply-To: <20150510095838.GF3338@piout.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 Content-Length: 1487 Lines: 41 On 10 May 2015 10:59 Alexandre Belloni wrote: > Hi, > > On 17/04/2015 at 15:23:33 +0100, S Twiss wrote : > > From: S Twiss > > > > Add RTC driver support for DA9062 [...] > This is an almost exact copy of drivers/rtc/rtc-da9063.c, apart from the > retry mechanism in read_time. Can you simply add support for the da9062 > in that driver? Hi Alexandre, Something similar is being discussed for the OnKey component of the DA9062. https://lkml.org/lkml/2015/4/24/304 It is only the OnKey and RTC components that are similar to the DA9063 chip and I was hoping to keep the 62 RTC separate in this case ... however it should definitely be possible to re-use the DA9063 RTC driver if this is your requirement. If this will block my submission of the DA9062 then I will drop the RTC from my next patch set and try to re-work the existing 63 RTC driver accordingly. I think this sort of thing has been done before: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/rtc-pm8xxx.c ... at first glance -- it seems to support that sort of thing. I guess it would be possible to rename the da9063-rtc to something more sensible like da9xxx-rtc.c if this goes ahead? Regards, Steve -- 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/