From: Joachim Eastwood <manabian@gmail.com>
To: alexandre.belloni@free-electrons.com, a.zummo@towertech.it
Cc: Joachim Eastwood <manabian@gmail.com>,
joshc@ni.com, rtc-linux@googlegroups.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] [PATCH v3 0/2] RTC support for NXP LPC18xx family
Date: Sat, 11 Jul 2015 19:28:48 +0200 [thread overview]
Message-ID: <1436635730-15617-1-git-send-email-manabian@gmail.com> (raw)
This patch set adds support for the RTC found on many NXP devices
including LPC178x/18xx/408x/43xx. The RTC provides calendar and
clock functionality together with alarm interrupt support.
The driver is a rework of an old driver by Kevin Wells. It has been
modified to support modern resource allocation, device tree and
generally cleaned up. Driver was originally written to support the
LPC24xx platform but since this platform isn't upstream support has
been removed. The LPC24xx name is still kept to preserve the origin
of this hardware block.
Been a while since the last version, but this version should address
all comments from Josh and Alexandre on v2. There has also been some
rework from my side. Please have a look.
changes since v2:
- rework hw init
- update Kconfig text
- remove unused registers defines
- misc clean ups
- rebase on 4.2-rc1
changes since v1:
- s/lpc2k/lpc24xx for better consistency
- fix Kconfig entry
- drop support for old versions for the ip block
Patch set is based on Linux v4.2-rc1.
Joachim Eastwood (2):
rtc: add rtc-lpc24xx driver
doc: dt: add documentation for nxp,lpc1788-rtc
.../devicetree/bindings/rtc/nxp,lpc1788-rtc.txt | 21 ++
drivers/rtc/Kconfig | 12 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-lpc24xx.c | 310 +++++++++++++++++++++
4 files changed, 344 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/nxp,lpc1788-rtc.txt
create mode 100644 drivers/rtc/rtc-lpc24xx.c
--
1.8.0
--
--
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-07-11 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 17:28 Joachim Eastwood [this message]
2015-07-11 17:28 ` [rtc-linux] [PATCH v3 1/2] rtc: add rtc-lpc24xx driver Joachim Eastwood
2015-07-13 17:37 ` [rtc-linux] " Josh Cartwright
2015-07-13 20:18 ` Joachim Eastwood
2015-07-11 17:28 ` [rtc-linux] [PATCH v3 2/2] doc: dt: add documentation for nxp,lpc1788-rtc Joachim Eastwood
2015-07-27 13:37 ` [rtc-linux] " Matt Porter
2015-08-05 8:50 ` Alexandre Belloni
2015-07-21 16:28 ` [rtc-linux] Re: [PATCH v3 0/2] RTC support for NXP LPC18xx family Alexandre Belloni
2015-07-21 16:46 ` Joachim Eastwood
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=1436635730-15617-1-git-send-email-manabian@gmail.com \
--to=manabian@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=joshc@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rtc-linux@googlegroups.com \
/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