From: Meelis Roos <mroos@linux.ee>
To: John Stultz <john.stultz@linaro.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH] alarmtimers: Handle late rtc module loading
Date: Mon, 20 Jun 2011 23:09:56 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1106202308050.29718@math.ut.ee> (raw)
In-Reply-To: <1308335616.3606.4.camel@work-vm>
> > One the PC, I get the following about RTC in dmesg:
> >
> > [ 0.319145] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > [ 3.614132] rtc_cmos 00:03: RTC can wake from S4
> > [ 3.614480] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> > [ 3.614582] rtc0: alarms up to one year, y3k, 114 bytes nvram
>
> I'll double check, but I suspect that "unable to open rtc device"
> message isn't new. The issue is that the rtc_cmos driver is built as a
> module, and the hctosys functionality is running before the module is
> loaded.
Yes. But I consider this a configuration error - to load modular rtc
driver and expect boottime clock setting from it works. It was by
mistake - the boottime options came later in time. Changed it to
statically compiled in PC CMOS RTC and it works fine.
> Hmmm. This maybe points to the need for some sort of callback system for
> when RTC devices are registered. Since most existing code is just hoping
> its available by late_init.
Is it really necessary?
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2011-06-20 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 1:34 John Stultz
2011-06-17 9:43 ` Meelis Roos
2011-06-17 18:33 ` John Stultz
2011-06-18 0:13 ` john stultz
2011-06-20 20:09 ` Meelis Roos [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=alpine.SOC.1.00.1106202308050.29718@math.ut.ee \
--to=mroos@linux.ee \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®