From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 5E3CADDEF0 for ; Tue, 4 Dec 2007 08:06:20 +1100 (EST) Subject: Re: [PATCH] Generic RTC class support for ppc_md.[gs]et_rtc_time From: David Woodhouse To: benh@kernel.crashing.org In-Reply-To: <1196714722.13230.224.camel@pasglop> References: <1196701493.13978.163.camel@pmac.infradead.org> <1196714722.13230.224.camel@pasglop> Content-Type: text/plain Date: Mon, 03 Dec 2007 21:06:14 +0000 Message-Id: <1196715974.13978.176.camel@pmac.infradead.org> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2007-12-04 at 07:45 +1100, Benjamin Herrenschmidt wrote: > On Mon, 2007-12-03 at 17:04 +0000, David Woodhouse wrote: > > It would be good to migrate the platform code to register RTC devices > > directly, but for now this will make them functional enough for most > > purposes... > > Wouldn't it be best to do the other way around at some stage ? Yes, definitely. We can migrate them one at a time to the RTC class. > We need to solve the problem of ppc_md. stuff being called by the core > in atomic contexts first though. Where from? -- dwmw2