linux-mips
[Top] [All Lists]

Re: a patch for generic MIPS RTC

To: macro@linux-mips.org
Subject: Re: a patch for generic MIPS RTC
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Mon, 05 Sep 2005 22:45:34 +0900 (JST)
Cc: spodstavin@ru.mvista.com, linux-mips@linux-mips.org, ralf@linux-mips.org
In-reply-to: <Pine.LNX.4.61L.0509051204140.29615@blysk.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1124355290.5441.45.camel@localhost.localdomain> <20050905.135422.112260934.nemoto@toshiba-tops.co.jp> <Pine.LNX.4.61L.0509051204140.29615@blysk.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
>>>>> On Mon, 5 Sep 2005 12:08:34 +0100 (BST), "Maciej W. Rozycki" 
>>>>> <macro@linux-mips.org> said:

macro>  That's how other architectures do this, see e.g.
macro> "arch/alpha/kernel/time.c".  Why should we be different, even
macro> for now?

Please elaborate more ?  Do you mean we should implement default
rtc_set_mmss() and take the rtc_lock in it ?  Or do you mean we should
take rtc_lock in each board-dependent rtc_set_time/rtc_set_time ?  

macro> Also the call is named rtc_set_mmss() for an unknown reason
macro> while all the others have set_rtc_mmss().

IIRC, you are (one of) the godfather of the function, aren't you?  :-)

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>