From: Philippe Reynes <tremyfr@gmail.com>
To: a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
shawn.guo@linaro.org, kernel@pengutronix.de,
linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Philippe Reynes <tremyfr@gmail.com>
Subject: [rtc-linux] [PATCH v3 0/6] add device tree support for mxc rtc
Date: Sat, 20 Jun 2015 19:12:34 +0200 [thread overview]
Message-ID: <1434820360-21935-1-git-send-email-tremyfr@gmail.com> (raw)
This serie add the device tree support for the mxc rtc driver.
To do this, three steps are required :
- define two rtc clocks for imx31 and imx35
- enhance mxc rtc driver to use two clocks (rtc and ipg)
- add device tree support to mxc rtc driver
Changelog:
v3: (thanks Fabio Estevam)
- fix typo in imx35 clock comment
v2: (thanks Shawn Guo and Alexandre Belloni)
- add a second clock to imx35
- split the add of clock in a separate patches
- split the dt documentation in a separate patch
Philippe Reynes (6):
imx31: add a second rtc clock
imx35: define two clocks for rtc
rtc: mxc: use a second rtc clock
rtc: mxc: add support of device tree
dt-binding: document the binding for mxc rtc
apf27: dt: add support of internal rtc
Documentation/devicetree/bindings/rtc/rtc-mxc.txt | 27 ++++++++++++
arch/arm/boot/dts/imx27-apf27.dts | 4 ++
arch/arm/boot/dts/imx27.dtsi | 10 +++++
arch/arm/mach-imx/clk-imx31.c | 3 +-
arch/arm/mach-imx/clk-imx35.c | 6 ++-
drivers/rtc/rtc-mxc.c | 45 ++++++++++++++++-----
6 files changed, 83 insertions(+), 12 deletions(-)
create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mxc.txt
--
1.7.4.4
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next reply other threads:[~2015-06-20 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 17:12 Philippe Reynes [this message]
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 1/6] imx31: add a second rtc clock Philippe Reynes
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 2/6] imx35: define two clocks for rtc Philippe Reynes
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 3/6] rtc: mxc: use a second rtc clock Philippe Reynes
2015-06-29 9:23 ` [rtc-linux] " Alexandre Belloni
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 4/6] rtc: mxc: add support of device tree Philippe Reynes
2015-06-29 9:24 ` [rtc-linux] " Alexandre Belloni
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 5/6] dt-binding: document the binding for mxc rtc Philippe Reynes
2015-06-22 13:59 ` [rtc-linux] " Rob Herring
2015-06-22 19:27 ` Alexandre Belloni
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 6/6] apf27: dt: add support of internal rtc Philippe Reynes
2015-06-29 9:26 ` [rtc-linux] " Alexandre Belloni
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=1434820360-21935-1-git-send-email-tremyfr@gmail.com \
--to=tremyfr@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.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