From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] rtc: stmp3xxx: DT bindings and wakealarm
Date: Mon, 4 Mar 2013 15:05:39 +0100 [thread overview]
Message-ID: <1362405948-12992-1-git-send-email-s.trumtrar@pengutronix.de> (raw)
Hi!
This series touches multiple things in the stmp3xxx RTC:
- DT bindings and selection for the crystal
- add sysfs entry for persistent regs 1-5
- check the copy controller on all writes/reads
Sorry for the multiple topics. If need be, I can split this up in multiple
series, but the series is in itself a little interdependent.
The series is based on v3.9-rc1.
Regards,
Steffen
Juergen Beisert (5):
MXS/i.MX28: add the possibility to define the used crystals via
device tree
MXS/i.MX28: add the possibility to define the external RTC crystal
MXS/i.MX28: prepare different clocking of the built-in RTC
MXS/i.MX28: there is more than one way to clock the RTC
MXS/i.MX28: enable RTC to wakeup the system
Steffen Trumtrar (4):
rtc: stmp3xxx: add sysfs entries for persistent regs
rtc: stmp3xxx: Re-enable active alarm
rtc: stmp3xxx: Check copy controller state
rtc: stmp3xxx: Replace wait_time function
arch/arm/boot/dts/imx28.dtsi | 19 +++
drivers/clk/mxs/clk-imx28.c | 20 ++-
drivers/rtc/rtc-stmp3xxx.c | 275 +++++++++++++++++++++++++++++++++++++++---
3 files changed, 297 insertions(+), 17 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-03-04 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 14:05 Steffen Trumtrar [this message]
2013-03-04 14:05 ` [PATCH 1/9] MXS/i.MX28: add the possibility to define the used crystals via device tree Steffen Trumtrar
2013-03-07 6:17 ` Shawn Guo
2013-03-04 14:05 ` [PATCH 2/9] MXS/i.MX28: add the possibility to define the external RTC crystal Steffen Trumtrar
2013-03-07 6:33 ` Shawn Guo
2013-03-04 14:05 ` [PATCH 3/9] MXS/i.MX28: prepare different clocking of the built-in RTC Steffen Trumtrar
2013-03-07 6:40 ` Shawn Guo
2013-03-04 14:05 ` [PATCH 4/9] MXS/i.MX28: there is more than one way to clock the RTC Steffen Trumtrar
2013-03-07 6:48 ` Shawn Guo
2013-03-07 8:19 ` Steffen Trumtrar
2013-03-04 14:05 ` [PATCH 5/9] MXS/i.MX28: enable RTC to wakeup the system Steffen Trumtrar
2013-03-04 14:05 ` [PATCH 6/9] rtc: stmp3xxx: add sysfs entries for persistent regs Steffen Trumtrar
2013-03-04 15:14 ` Grant Likely
2013-03-05 8:02 ` Steffen Trumtrar
2013-03-06 13:27 ` Steffen Trumtrar
2013-03-04 14:05 ` [PATCH 7/9] rtc: stmp3xxx: Re-enable active alarm Steffen Trumtrar
2013-03-04 14:05 ` [PATCH 8/9] rtc: stmp3xxx: Check copy controller state Steffen Trumtrar
2013-03-04 14:05 ` [PATCH 9/9] rtc: stmp3xxx: Replace wait_time function Steffen Trumtrar
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=1362405948-12992-1-git-send-email-s.trumtrar@pengutronix.de \
--to=s.trumtrar@pengutronix.de \
--cc=linux-arm-kernel@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).