linux-mips
[Top] [All Lists]

Re: [MIPS] Use generic NTP code for all MIPS platforms

To: vagabon.xyz@gmail.com
Subject: Re: [MIPS] Use generic NTP code for all MIPS platforms
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Tue, 14 Aug 2007 23:12:55 +0900 (JST)
Cc: linux-mips@linux-mips.org
In-reply-to: <46C0A83B.2090003@gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <46C07F36.1070308@gmail.com> <20070814.020229.29578157.anemo@mba.ocn.ne.jp> <46C0A83B.2090003@gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On Mon, 13 Aug 2007 20:51:39 +0200, Franck Bui-Huu <vagabon.xyz@gmail.com> 
wrote:
> Well a more general question could be how is the RTC class layer
> supposed to interact with the kernel ?
> 
> Should RTC class layer implement a general service to update/read the
> RTC, IOW should it implement {read,update}_persistent_clock() ?

Some difficulties are:

* timekeeping subsystem calls {read,update}_persistent_clock() with
  irq-disabled.  But most RTC class routines might sleep.

* RTC class can have multiple RTCs on the system.

* There are already some conflicting features in RTC class ---
  rtc_suspend and rtc_resume try to adjust the wall clock.

* IIRC Some people said "NTP sync can be done all in userland" ;-)


Does anybody know if there was "general consensus" on this topic?

---
Atsushi Nemoto

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