From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/5] drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs
Date: Thu, 15 Jan 2015 22:48:37 +0100 [thread overview]
Message-ID: <87egqv7m16.fsf@natisbad.org> (raw)
In-Reply-To: <1421342601-20384-3-git-send-email-gregory.clement@free-electrons.com> (Gregory CLEMENT's message of "Thu, 15 Jan 2015 18:23:18 +0100")
Hi Gregory,
Gregory CLEMENT <gregory.clement@free-electrons•com> writes:
> The new mvebu SoCs come with a new RTC driver. This patch adds the
> support for this new IP which is currently found in the Armada 38x
> SoCs.
>
> This RTC provides two alarms, but only the first one is used in the
> driver. The RTC also allows using periodic interrupts.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons•com>
> ---
> drivers/rtc/Kconfig | 10 ++
> drivers/rtc/Makefile | 1 +
> drivers/rtc/rtc-armada38x.c | 320 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 331 insertions(+)
> create mode 100644 drivers/rtc/rtc-armada38x.c
FWIW:
Reviewed-by: Arnaud Ebalard <arno@natisbad•org>
Cheers,
a+
next prev parent reply other threads:[~2015-01-15 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:23 [PATCH v4 0/5] Add a new RTC driver for recent mvebu SoCs Gregory CLEMENT
2015-01-15 17:23 ` [PATCH v4 1/5] rtc: armada38x: Add the device tree binding documentation Gregory CLEMENT
2015-01-15 17:23 ` [PATCH v4 2/5] drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs Gregory CLEMENT
2015-01-15 21:48 ` Arnaud Ebalard [this message]
2015-01-15 17:23 ` [PATCH v4 3/5] MAINTAINERS: Add the RTC driver for the Armada38x Gregory CLEMENT
2015-01-15 17:23 ` [PATCH v4 4/5] ARM: mvebu: add Device Tree description of RTC on Armada 38x Gregory CLEMENT
2015-01-15 17:23 ` [PATCH v4 5/5] ARM: mvebu: enable Armada 38x RTC driver in mvebu_v7_defconfig Gregory CLEMENT
2015-02-04 9:04 ` [PATCH v4 0/5] Add a new RTC driver for recent mvebu SoCs Gregory CLEMENT
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=87egqv7m16.fsf@natisbad.org \
--to=arno@natisbad$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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