From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Use generic NTP code for all MIPS platforms
Date: Tue, 14 Aug 2007 11:29:13 +0100 [thread overview]
Message-ID: <20070814102913.GD16958@linux-mips.org> (raw)
In-Reply-To: <20070814.003242.59465104.anemo@mba.ocn.ne.jp>
On Tue, Aug 14, 2007 at 12:32:42AM +0900, Atsushi Nemoto wrote:
> config GENERIC_CMOS_UPDATE
> bool
> default y
>
> I think there are no point using GENERIC_CMOS_UPDATE for users of the
> new-style RTC_CLASS drivers or platforms with no RTC.
Platforms with no RTC are easy to handle, just throw in a dummy
implementation of all the RTC functions. Or if you just don't want
RTC updates, set no_sync_cmos_clock = 1.
Several platforms had their own timer interrupt handlers overriding the
generic interrupt handler and breaking the NTP. In most cases I doubt
this was a design decission so I had to go for a solution that makes
NTP work by default.
> There are some possible ways:
>
> A) Make default of GENERIC_CMOS_UPDATE to "n" and select it explicitly
> on platforms which need it.
>
> B) Make default of GENERIC_CMOS_UPDATE depends on CONFIG_RTC_CLASS.
>
> C) set no_sync_cmos_clock to 0 on time_init() if rtc_mips_set_mmss was
> NULL and rtc_mips_set_time and was null_rtc_set_time.
>
> And combinations ot variations of those...
You may want to look at my time changes. One of the patches turns all
the excessive function pointer business we have in the MIPS time code
upside down in preparation for the dyntick code.
Ralf
prev parent reply other threads:[~2007-08-14 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20023068AbXHMO0W/20070813142622Z+9352@ftp.linux-mips.org>
2007-08-13 15:32 ` [MIPS] Use generic NTP code for all MIPS platforms Atsushi Nemoto
2007-08-13 15:56 ` Franck Bui-Huu
2007-08-13 17:02 ` Atsushi Nemoto
2007-08-13 18:51 ` Franck Bui-Huu
2007-08-14 14:12 ` Atsushi Nemoto
2007-08-14 15:26 ` Maciej W. Rozycki
2007-08-14 10:29 ` Ralf Baechle [this message]
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=20070814102913.GD16958@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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