From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linus-amlogic@lists.infradead.org
Subject: second round of rtc
Date: Fri, 24 Jun 2016 18:36:09 +0100 [thread overview]
Message-ID: <1466789773-1609-1-git-send-email-ben.dooks@codethink.co.uk> (raw)
This is the second RFC for the RTC support. I have
gone through and applied most of the suggested cleanups
and done a bit more tidying.
The driver has a couple of extra debug prints, and also
has a fixed rtc register write code (wrong order) so that
it can now set a time from hwclock.
This has been tested on the an ODroid-C1 with battery
connected to it.
next reply other threads:[~2016-06-24 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 17:36 Ben Dooks [this message]
2016-06-24 17:36 ` [RFCv2 1/4] rtc: support for amlogic meson rtc Ben Dooks
2016-06-24 17:36 ` [RFCv2 2/4] meson-rtc: add device-tree binding Ben Dooks
2016-06-24 17:36 ` [RFCv2 3/4] ARM: dts: amlogic: add rtc node for meson8b Ben Dooks
2016-06-24 17:36 ` [RFCv2 4/4] ARM: meson: enable RTC for ODRoid-C1 Ben Dooks
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=1466789773-1609-1-git-send-email-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linus-amlogic@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).