From: John Stultz <john.stultz@linaro.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
John Whitmore <arigead@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexander Holler <holler@ahsoftware.de>
Subject: [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules
Date: Fri, 27 Jun 2014 10:27:09 -0700 [thread overview]
Message-ID: <1403890031-26419-1-git-send-email-john.stultz@linaro.org> (raw)
Its been pointed out that the RTC hctosys functionality doesn't
work well with RTC modules, which may not be loaded until after
late_init().
While there have been other attempts to sovle this, this patchset
is a very quick 10 minute effort to show how I'd try to resolve
this. There likely are still issues here, but I'd be happy to
make fixes and adjustments to ensure it works.
Feedback and comments always appreciated!
-john
Cc: John Whitmore <arigead@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>
Cc: Alexander Holler <holler@ahsoftware.de>
John Stultz (2):
time: Introduce do_first_settimeofday()
rtc: Rework hctosys so that it is called on RTC registration
drivers/rtc/class.c | 2 ++
drivers/rtc/hctosys.c | 19 +++++++----------
include/linux/rtc.h | 6 ++++++
include/linux/time.h | 2 ++
kernel/time/timekeeping.c | 54 ++++++++++++++++++++++++++++++++++++++---------
5 files changed, 62 insertions(+), 21 deletions(-)
--
1.9.1
next reply other threads:[~2014-06-27 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:27 John Stultz [this message]
2014-06-27 17:27 ` [PATCH 1/2][RFC] time: Introduce do_first_settimeofday() John Stultz
2014-06-27 17:27 ` [PATCH 2/2][RFC] rtc: Rework hctosys so that it is called on RTC registration John Stultz
2014-06-28 7:18 ` [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules Alexander Holler
2014-06-28 7:32 ` Alexander Holler
2014-06-28 18:54 ` Marc Dietrich
2014-06-28 20:50 ` Alexander Holler
2014-06-30 19:37 ` Alessandro Zummo
2014-07-01 18:42 ` Alexander Holler
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=1403890031-26419-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=a.zummo@towertech.it \
--cc=arigead@gmail.com \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome