Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759106AbZCBJyp (ORCPT ); Mon, 2 Mar 2009 04:54:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756803AbZCBJyc (ORCPT ); Mon, 2 Mar 2009 04:54:32 -0500 Received: from vervifontaine.sonytel.be ([80.88.33.193]:62817 "EHLO vervifontaine.sonycom.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752886AbZCBJya (ORCPT ); Mon, 2 Mar 2009 04:54:30 -0500 Date: Mon, 2 Mar 2009 10:54:14 +0100 (CET) From: Geert Uytterhoeven To: Richard Zidlicky cc: Alessandro Zummo , rtc-linux@googlegroups.com, David Woodhouse , linux-parisc@vger.kernel.org, Linux Kernel Development , David@ozlabs.org, Kyle McMartin , Linux/PPC Development , Linux/m68k , Benjamin Herrenschmidt Subject: Re: [rtc-linux] Re: [PATCH/RFC 0/5] Generic RTC class driver In-Reply-To: <20090227185514.GA1071@linux-m68k.org> Message-ID: References: <1235144809-32468-1-git-send-email-Geert.Uytterhoeven@sonycom.com> <20090220170454.04382e9e@i1501.lan.towertech.it> <1235511327.18632.73.camel@macbook.infradead.org> <20090224231154.60ba18d6@i1501.lan.towertech.it> <1235514727.18632.93.camel@macbook.infradead.org> <20090225111836.621412c1@i1501.lan.towertech.it> <20090227185514.GA1071@linux-m68k.org> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2576 Lines: 63 On Fri, 27 Feb 2009, Richard Zidlicky wrote: > On Wed, Feb 25, 2009 at 11:18:36AM +0100, Alessandro Zummo wrote: > > On Wed, 25 Feb 2009 11:00:13 +0100 (CET) > > Geert Uytterhoeven wrote: > > > > > I didn't know NTP was broken with RTC class drivers? > > > > > > So we should actually keep on using genrtc instead of rtc-ppc/rtc-generic for > > > now? ;-) > > > > broken here means that the kernel won't save the time to the hardware > > rtc every 11 minutes as it used to do. normal NTP operations are unaffected. > > seems like so far ppc is the only architecture attempting to implement it > correctly, all others either have it unimplemented or use the broken > by design set_rtc_mmss method. > Also note that in most cases hwclock has much better possibilities > to do a good job. > > Regarding genrtc vs rtc-ppc/rtc-generic it is worth noting that genrtc > provides RTC_UIE emulation which is of some use for exotic programs like > "chrony". > Afaics this is also the only situation without a good userspace workaround > and chrony never worked well for me so I have nothing against junking the > code. What about CONFIG_RTC_INTF_DEV_UIE_EMUL for RTC class devices? > Regarding a possible reorganisation from the generic to all separate drivers > I agree that the habit of putting rtc-chip specific code in asm-generic is > confusing at best. > In many cases such code might be better placed in drivers/rtc or > include/linux/rtc/chipname. > > Imho this does not preclude the possibility to use a generic framework. While > there certainly are valid reasons to have separate drivers in some cases > I do not see much value in rewriting everything as separate drivers where > the generic framework works well. Indeed. You can have a working RTC class driver for lots of hardware by just writing ca. 100 lines of code on top of the generic framework. With kind regards, Geert Uytterhoeven Software Architect Sony Techsoft Centre Europe The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium Phone: +32 (0)2 700 8453 Fax: +32 (0)2 700 8622 E-mail: Geert.Uytterhoeven@sonycom.com Internet: http://www.sony-europe.com/ A division of Sony Europe (Belgium) N.V. VAT BE 0413.825.160 · RPR Brussels Fortis · BIC GEBABEBB · IBAN BE41293037680010 -- 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/