From: Arnaud Ebalard <arno@natisbad.org>
To: "Andrew Morton" <akpm@linux-foundation.org>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Peter Huewe <peter.huewe@infineon.com>,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <treding@nvidia.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Darshana Padmadas <darshanapadmadas@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Rob Landley <rob@landley.net>,
rtc-linux@googlegroups.com, Jason Cooper <jason@lakedaemon.net>,
Guenter Roeck <linux@roeck-us.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 0/3] Alarm support for ISL12057 + RFC dt property
Date: Tue, 16 Dec 2014 00:54:13 +0100 [thread overview]
Message-ID: <cover.1418687005.git.arno@natisbad.org> (raw)
Hi,
Changes since v0:
- Basic alarm support is now the first patch of the series with nothing
fancy in it: as per Uwe's request, all the "Chip IRQ#2 is not routed
to the SoC but device can still be woken up with the alarm" is in the
second patch. Uwe, can you review that one, so that Andrew can then
merge it if it is ok?
- Second patch has simple changes going on top of first patch to
support the use case for current in-tree users, i.e. ReadyNAS 102,
104 and 2120. It's a simple property with complete documentation
about what it does and does not.
- Third and last patch add that property to 102, 104 nd 2120 .dts
files (in a single patch as suggested by Jason)
Comments welcome,
Cheers,
a+
Arnaud Ebalard (3):
rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver
rtc: rtc-isl12057: add isil,irq2-can-wakeup-machine property for in-tree users
ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN104 and RN2120
.../devicetree/bindings/rtc/isil,isl12057.txt | 78 +++++
arch/arm/boot/dts/armada-370-netgear-rn102.dts | 1 +
arch/arm/boot/dts/armada-370-netgear-rn104.dts | 1 +
arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 1 +
drivers/rtc/rtc-isl12057.c | 346 ++++++++++++++++++++-
5 files changed, 419 insertions(+), 8 deletions(-)
create mode 100644 Documentation/devicetree/bindings/rtc/isil,isl12057.txt
--
2.1.1
next reply other threads:[~2014-12-15 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:54 Arnaud Ebalard [this message]
2014-12-15 23:54 ` [PATCHv1 1/3] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver Arnaud Ebalard
2014-12-16 10:08 ` Uwe Kleine-König
2014-12-16 12:07 ` Arnaud Ebalard
2014-12-16 21:47 ` Uwe Kleine-König
2014-12-16 23:05 ` Mark Brown
2014-12-15 23:54 ` [PATCHv1 2/3] rtc: rtc-isl12057: add isil,irq2-can-wakeup-machine property for in-tree users Arnaud Ebalard
2014-12-15 23:55 ` [PATCHv1 3/3] ARM: mvebu: ISL12057 rtc chip can now wake up RN102, RN102 and RN2120 Arnaud Ebalard
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=cover.1418687005.git.arno@natisbad.org \
--to=arno@natisbad.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=darshanapadmadas@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.huewe@infineon.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@wwwdotorg.org \
--cc=treding@nvidia.com \
--cc=uwe@kleine-koenig.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).