From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
a.zummo@towertech.it, rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH v2 0/2] add Alphascale asm9260 RTC driver
Date: Sat, 20 Feb 2016 05:38:33 +0100 [thread overview]
Message-ID: <20160220043833.GF2222@piout.net> (raw)
In-Reply-To: <1454442971-25225-1-git-send-email-linux@rempel-privat.de>
On 02/02/2016 at 20:56:09 +0100, Oleksij Rempel wrote :
> This patch set provide support for RTC controller found on Alphascale
> ASM9260 SoC.
>
> v2:
> - change license to GPLv2 and later
> - remove HW_RTC_AUX and HW_RTC_AUXEN. Thay was taken from reference driver.
> Documentation do not provide any info about it. According to my tests
> this regs are not available on asm9260.
> - remove calibration from DT. It will be beter to set it over sysfs.
>
> Oleksij Rempel (2):
> rtc: add rtc-asm9260 driver
> doc: dt: add documentation for alphascale,asm9260-rtc
>
> .../bindings/rtc/alphascale,asm9260-rtc.txt | 19 ++
> drivers/rtc/Kconfig | 10 +
> drivers/rtc/Makefile | 1 +
> drivers/rtc/rtc-asm9260.c | 355 +++++++++++++++++++++
> 4 files changed, 385 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/alphascale,asm9260-rtc.txt
> create mode 100644 drivers/rtc/rtc-asm9260.c
>
Applied, thanks!
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
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 prev parent reply other threads:[~2016-02-20 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 8:40 [rtc-linux] [PATCH 0/2] add Alphascale asm9260 RTC driver Oleksij Rempel
2016-01-29 8:40 ` [rtc-linux] [PATCH 1/2] rtc: add rtc-asm9260 driver Oleksij Rempel
2016-02-01 16:05 ` [rtc-linux] " Alexandre Belloni
2016-02-02 8:24 ` Oleksij Rempel
2016-01-29 8:40 ` [rtc-linux] [PATCH 2/2] doc: dt: add documentation for alphascale,asm9260-rtc Oleksij Rempel
2016-02-01 15:27 ` [rtc-linux] " Rob Herring
2016-02-01 15:55 ` Alexandre Belloni
2016-02-02 8:46 ` Oleksij Rempel
2016-02-02 10:28 ` Alexandre Belloni
2016-02-02 19:56 ` [rtc-linux] [PATCH v2 0/2] add Alphascale asm9260 RTC driver Oleksij Rempel
2016-02-02 19:56 ` [rtc-linux] [PATCH v2 1/2] rtc: add rtc-asm9260 driver Oleksij Rempel
2016-02-02 19:56 ` [rtc-linux] [PATCH v2 2/2] doc: dt: add documentation for alphascale,asm9260-rtc Oleksij Rempel
2016-02-02 21:12 ` [rtc-linux] " Rob Herring
2016-02-20 4:38 ` Alexandre Belloni [this message]
2016-02-02 8:42 ` [rtc-linux] Re: [PATCH " Oleksij Rempel
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=20160220043833.GF2222@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=robh+dt@kernel.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