From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux-rtc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH 00/16] rtc: rv3029: cleanup and features
Date: Sat, 14 Dec 2019 23:10:06 +0100 [thread overview]
Message-ID: <20191214221022.622482-1-alexandre.belloni@bootlin.com> (raw)
Hi,
This series cleans up the rv3029 driver and adds a few features:
RTC_VL_READ and RTC_VL_CLR support, correct rtc range enforcement, NVRAM
support.
This series depends on the previously sent RTC_VL_READ unification.
Alexandre Belloni (16):
rtc: rv3029: use proper name for the driver
rtc: rv3029: let regmap validate the register ranges
rtc: rv3029: remove open coded regmap_update_bits
rtc: rv3029: remove race condition when update STATUS
rtc: rv3029: avoid reading the status register uselessly
rtc: rv3029: get rid of rv3029_get_sr
rtc: rv3029: simplify rv3029_alarm_irq_enable
rtc: rv3029: simplify rv3029_set_alarm
rtc: rv3029: drop rv3029_read_regs and rv3029_write_regs
rtc: rv3029: add RTC_VL_READ and RTC_VL_CLEAR support
rtc: rv3029: correctly handle PON and VLOW2
rtc: rv3029: convert to devm_rtc_allocate_device
rtc: rv3029: let the core handle rtc range
rtc: rv3029: remove useless error messages
rtc: rv3029: annotate init and exit functions
rtc: rv3029: add nvram support
drivers/rtc/rtc-rv3029c2.c | 444 +++++++++++++++----------------------
include/linux/rtc.h | 1 +
2 files changed, 185 insertions(+), 260 deletions(-)
--
2.23.0
next reply other threads:[~2019-12-14 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 22:10 Alexandre Belloni [this message]
2019-12-14 22:10 ` [PATCH 01/16] rtc: rv3029: use proper name for the driver Alexandre Belloni
2019-12-14 22:10 ` [PATCH 02/16] rtc: rv3029: let regmap validate the register ranges Alexandre Belloni
2019-12-14 22:10 ` [PATCH 03/16] rtc: rv3029: remove open coded regmap_update_bits Alexandre Belloni
2019-12-14 22:10 ` [PATCH 04/16] rtc: rv3029: remove race condition when update STATUS Alexandre Belloni
2019-12-14 22:10 ` [PATCH 05/16] rtc: rv3029: avoid reading the status register uselessly Alexandre Belloni
2019-12-14 22:10 ` [PATCH 06/16] rtc: rv3029: get rid of rv3029_get_sr Alexandre Belloni
2019-12-14 22:10 ` [PATCH 07/16] rtc: rv3029: simplify rv3029_alarm_irq_enable Alexandre Belloni
2019-12-14 22:10 ` [PATCH 08/16] rtc: rv3029: simplify rv3029_set_alarm Alexandre Belloni
2019-12-14 22:10 ` [PATCH 09/16] rtc: rv3029: drop rv3029_read_regs and rv3029_write_regs Alexandre Belloni
2019-12-14 22:10 ` [PATCH 10/16] rtc: rv3029: add RTC_VL_READ and RTC_VL_CLEAR support Alexandre Belloni
2019-12-14 22:10 ` [PATCH 11/16] rtc: rv3029: correctly handle PON and VLOW2 Alexandre Belloni
2019-12-14 22:10 ` [PATCH 12/16] rtc: rv3029: convert to devm_rtc_allocate_device Alexandre Belloni
2019-12-14 22:10 ` [PATCH 13/16] rtc: rv3029: let the core handle rtc range Alexandre Belloni
2019-12-14 22:10 ` [PATCH 14/16] rtc: rv3029: remove useless error messages Alexandre Belloni
2019-12-14 22:10 ` [PATCH 15/16] rtc: rv3029: annotate init and exit functions Alexandre Belloni
2019-12-14 22:10 ` [PATCH 16/16] rtc: rv3029: add nvram support 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=20191214221022.622482-1-alexandre.belloni@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).