From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RTC for 7.0
Date: Sun, 22 Feb 2026 02:33:26 +0100 [thread overview]
Message-ID: <202602220133264688bffa@mail.local> (raw)
Hello Linus,
Here is the RTC subsystem pull request for 7.0. There are a few fixes
and improvement this cycle.
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/rtc-7.0
for you to fetch changes up to 969c3cca0f3b88682cd833cee4cf01b0915629a3:
rtc: ds1390: fix number of bytes read from RTC (2026-02-20 23:12:25 +0100)
----------------------------------------------------------------
RTC for 7.0
Drivers:
- loongson: Loongson-2K0300 support
- s35390a: nvmem support
- zynqmp: rework calibration
----------------------------------------------------------------
Andreas Gabriel-Platschek (1):
rtc: ds1390: fix number of bytes read from RTC
Anthony Pighin (Nokia) (1):
rtc: interface: Alarm race handling should not discard preceding error
Binbin Zhou (3):
dt-bindings: rtc: loongson: Correct Loongson-1C interrupts property
dt-bindings: rtc: loongson: Document Loongson-2K0300 compatible
rtc: loongson: Add Loongson-2K0300 support
Jinjie Ruan (1):
rtc: class: Remove duplicate check for alarm
John Keeping (1):
rtc: pcf8563: use correct of_node for output clock
Lorenz Brun (1):
rtc: s35390a: implement nvmem support
Ovidiu Panait (1):
dt-bindings: rtc: renesas,rz-rtca3: Add RZ/V2N support
Peter Robinson (1):
rtc: nvvrs: Add ARCH_TEGRA to the NV VRS RTC driver
Randy Dunlap (1):
rtc: max31335: use correct CONFIG symbol in IS_REACHABLE()
Rouven Czerwinski (1):
rtc: optee: simplify OP-TEE context match
Sebastian Andrzej Siewior (1):
rtc: amlogic-a4: Remove IRQF_ONESHOT
Svyatoslav Ryhel (1):
dt-bindings: rtc: cpcap: convert to schema
Tomas Melin (5):
rtc: zynqmp: correct frequency value
rtc: zynqmp: check calibration max value
rtc: zynqmp: rework read_offset
rtc: zynqmp: rework set_offset
rtc: zynqmp: use dynamic max and min offset ranges
.../devicetree/bindings/rtc/cpcap-rtc.txt | 18 ------
.../devicetree/bindings/rtc/loongson,rtc.yaml | 13 ++++
.../bindings/rtc/motorola,cpcap-rtc.yaml | 32 +++++++++
.../devicetree/bindings/rtc/renesas,rz-rtca3.yaml | 5 +-
drivers/rtc/Kconfig | 1 +
drivers/rtc/class.c | 2 +-
drivers/rtc/interface.c | 2 +-
drivers/rtc/rtc-amlogic-a4.c | 2 +-
drivers/rtc/rtc-ds1390.c | 2 +-
drivers/rtc/rtc-loongson.c | 71 +++++++++++++-------
drivers/rtc/rtc-max31335.c | 6 +-
drivers/rtc/rtc-optee.c | 5 +-
drivers/rtc/rtc-pcf8563.c | 2 +-
drivers/rtc/rtc-s35390a.c | 32 +++++++++
drivers/rtc/rtc-zynqmp.c | 75 ++++++++++++----------
15 files changed, 179 insertions(+), 89 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/rtc/cpcap-rtc.txt
create mode 100644 Documentation/devicetree/bindings/rtc/motorola,cpcap-rtc.yaml
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2026-02-22 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 1:33 Alexandre Belloni [this message]
2026-02-22 20:18 ` [GIT PULL] RTC for 7.0 pr-tracker-bot
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=202602220133264688bffa@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=torvalds@linux-foundation.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