From: "Heiko Stübner" <heiko@sntech.de>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
devicetree@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Mike Turquette <mturquette@linaro.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v4 0/2] Add support for hym8563 rtcs
Date: Mon, 9 Dec 2013 22:19:10 +0100 [thread overview]
Message-ID: <201312092219.11342.heiko@sntech.de> (raw)
This series adds support for the Haoyu Microelectronics HYM8563 rtc. This
chip is often used in designs around the Cortex-A9 SoCs from Rockchip to
provide rtc functionality and the 32kHz suspend clock the SoC needs.
changes since v3:
- follow suggestion from Mark Brown to use the interrupt without the gpio
changes since v2:
- get size for devm_kzalloc from struct not from pointer
changes since v1:
- add haoyu prefix to vendor-prefixes.txt
- use gpio_to_irq to get the alarm interrupt instead of specifying it
separately to the gpio itself
Heiko Stuebner (2):
dt-bindings: add hym8563 binding
rtc: add hym8563 rtc-driver
.../devicetree/bindings/rtc/haoyu,hym8563.txt | 27 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-hym8563.c | 601 ++++++++++++++++++++
5 files changed, 641 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt
create mode 100644 drivers/rtc/rtc-hym8563.c
--
1.7.10.4
next reply other threads:[~2013-12-09 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 21:19 Heiko Stübner [this message]
2013-12-09 21:20 ` [PATCH v4 1/2] dt-bindings: add hym8563 binding Heiko Stübner
2013-12-10 11:17 ` Mark Brown
2013-12-09 21:21 ` [PATCH v4 2/2] rtc: add hym8563 rtc-driver Heiko Stübner
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=201312092219.11342.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=a.zummo@towertech.it \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=richard.weinberger@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@wwwdotorg.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