All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: linux-kernel@vger.kernel.or
Subject: RTC subsystem and 11 min rtc update
Date: Wed, 21 May 2008 23:57:51 +0200	[thread overview]
Message-ID: <20080521215751.GA12343@frolo.macqel> (raw)
In-Reply-To: <20080520140744.GA6427@frolo.macqel>

Hello everybody,

I have linux-2.6.25-rc6 running on a board with an i2c rtc chip,
and synchronized to a ntp server.  When my board starts, the current
time is correctly read from the rtc chip, but ...

I noticed that my rtc chip does not get updated by the kernel every 11 min,
on my powerpc board, just like it would be on all other architectures.

Paul Mackerras told me that that is now supposed to be done by the code
inside #ifdef CONFIG_GENERIC_CMOS_UPDATE in kernel/time/ntp.c.

I agree that is a good place.

But, here CONFIG_GENERIC_CMOS_UPDATE is well defined and an i2c clock also,
and my rtc clock is not updated.  I see kernel/time/ntp.c::sync_cmos_clock
calling arch/powerpc/kernel/time.c::update_persistent_clock, where
ppc_md.set_rtc_time is NULL. ppc_md.get_rtc_time is NULL as well, but
that does not prevent the initial reading of the rtc clock during the startup
of the kernel.

Should update_persistent_clock not be directly part of the rtc subsystem,
instead of falling in a detour or a dead-end in the arch subsystem ?

Philippe

  reply	other threads:[~2008-05-21 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 10:58 ppc -> powerpc : where is 11 min rtc update gone ? Philippe De Muyter
2008-05-20 11:10 ` Paul Mackerras
2008-05-20 14:07   ` powerpc + i2c/rtc : where is the 11 min update ? Philippe De Muyter
2008-05-21 21:57     ` Philippe De Muyter [this message]
2008-05-21 22:18       ` RTC subsystem and 11 min rtc update Maciej W. Rozycki

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=20080521215751.GA12343@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=linux-kernel@vger.kernel.or \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.