linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
	rtc-linux@googlegroups.com, Richard Zidlicky <rz@linux-m68k.org>,
	linux-parisc@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	David@ozlabs.org, Kyle McMartin <kyle@mcmartin.ca>,
	Linux/PPC Development <linuxppc-dev@ozlabs.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [rtc-linux] [PATCH/RFC 0/5] Generic RTC class driver
Date: Wed, 25 Feb 2009 10:54:33 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.2.00.0902251051370.4063@vixen.sonytel.be> (raw)
In-Reply-To: <1235511327.18632.73.camel@macbook.infradead.org>

On Wed, 25 Feb 2009, David Woodhouse wrote:
> On Mon, 2009-02-23 at 13:34 +0100, Geert Uytterhoeven wrote:
> > >    my opinion on this kind of stuff is that I want to avoid the layering
> > >  of implementations under the rtc subsystem. I'd rather prefer that each
> > >  rtc device had its own driver. 
> > >  
> > >   I've made error in the past, by accepting such kind of drivers, and
> > >  would like to avoid that it happens again.
> > 
> > So you want us to kill the ppc_md.[gs]et_rtc_time() [ppc], mach_hwclk() [m68k],
> > mach_gettod() [m68knommu] (and probably a few other) abstractions, and move all
> > RTC code out of arch/ into seperate drivers under drivers/rtc/ instead?
> 
> That's the ideal... although did we get NTP sync working again yet?
> 
> The rtc-ppc driver was intended as a short-term workaround so that we
> can enable the generic RTC class (which was required for PA Semi
> Electra, iirc), and still have stuff work on other platforms.

Sure. The only differences between your rtc-ppc driver and rtc-parisc were:
  - rtc-ppc uses the PPC RTC abstraction (ppc_md.[gs]et_rtc_time()),
    while rtc-parisc uses the genrtc abstraction layer ([gs]et_rtc_time()),
    which is shared by several architectures,
  - rtc-ppc has the platform device built-in in the driver, while rtc-parisc
    relies on the creation of the platform device in platform code.

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

  parent reply	other threads:[~2009-02-25  9:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 15:46 [PATCH/RFC 0/5] Generic RTC class driver Geert Uytterhoeven
2009-02-20 15:46 ` [PATCH/RFC 1/5] rtc-parisc: Add missing module alias Geert Uytterhoeven
2009-02-20 15:46   ` [PATCH/RFC 2/5] pa-risc: Rename rtc-parisc to rtc-generic Geert Uytterhoeven
2009-02-20 15:46     ` [PATCH/RFC 3/5] m68k: Enable rtc-generic Geert Uytterhoeven
2009-02-20 15:46       ` [PATCH/RFC 4/5] powerpc: Enable rtc-generic, and kill rtc-ppc Geert Uytterhoeven
2009-02-20 15:46         ` [PATCH/RFC 5/5] rtc: Kill genrtc, as all its users have been converted to rtc-generic Geert Uytterhoeven
2009-02-20 16:04 ` [rtc-linux] [PATCH/RFC 0/5] Generic RTC class driver Alessandro Zummo
2009-02-23 12:34   ` Geert Uytterhoeven
2009-02-23 15:05     ` [rtc-linux] " Alessandro Zummo
2009-02-24 17:56       ` Geert Uytterhoeven
2009-02-24 18:37         ` Alessandro Zummo
2009-02-25  1:14           ` Brad Boyer
2009-02-25  9:58             ` Geert Uytterhoeven
2009-02-24 21:35     ` [rtc-linux] " David Woodhouse
2009-02-24 22:11       ` Alessandro Zummo
2009-02-24 22:32         ` David Woodhouse
2009-02-25 10:00           ` Geert Uytterhoeven
2009-02-25 10:18             ` [rtc-linux] " Alessandro Zummo
2009-02-27 17:17               ` Maciej W. Rozycki
2009-02-27 17:19                 ` Alessandro Zummo
2009-02-27 18:55               ` Richard Zidlicky
2009-03-02  9:54                 ` Geert Uytterhoeven
2009-03-02 10:03                   ` Alessandro Zummo
2009-03-02 10:28                     ` Geert Uytterhoeven
2009-03-02 11:09                       ` Alessandro Zummo
2009-03-03 10:41                         ` Geert Uytterhoeven
2009-03-03 13:53                           ` Alessandro Zummo
2009-03-03 19:06                           ` Paul Mundt
2009-03-04  8:26                             ` Geert Uytterhoeven
2009-03-04 12:47                               ` Alessandro Zummo
2009-03-04 12:51                                 ` Geert Uytterhoeven
2009-02-25  9:54       ` Geert Uytterhoeven [this message]
2009-02-24 18:46 ` Helge Deller
2009-02-25  9:54   ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.00.0902251051370.4063@vixen.sonytel.be \
    --to=geert.uytterhoeven@sonycom.com \
    --cc=David@ozlabs.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=rz@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).