From: Binbin Zhou <zhoubinbin@loongson.cn>
To: Binbin Zhou <zhoubb.aaron@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Cc: Xiaochuang Mao <maoxiaochuan@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org,
Keguang Zhang <keguang.zhang@gmail.com>,
Binbin Zhou <zhoubinbin@loongson.cn>
Subject: [PATCH v3 0/3] RTC: Add Loongson-2K0300 support
Date: Sat, 17 Jan 2026 10:26:47 +0800 [thread overview]
Message-ID: <cover.1768616276.git.zhoubinbin@loongson.cn> (raw)
Hi all:
This patch set introduces the Loongson-2K0300 RTC, which has a similar
hardware design to the Loongson-1B, but without the alarm feature.
Thanks.
Binbin
==========
V3:
- Add Reviewed-by tag from Huacai, thanks.
Patch (1/3):
- Update commit title: dt-binding -> dt-bindings;
- Update the commit message to describe the binding ABI breaking.
- Drop `not` and flip the 'then' and 'else' schemas around.
Patch (2/3):
- Update commit title: dt-binding -> dt-bindings.
Link to V2:
https://lore.kernel.org/all/cover.1767663073.git.zhoubinbin@loongson.cn/
V2:
Patch (1/3):
- New patch, correct Loongson-1C `interrupts` property;
Patch (2/3):
- Drop Loongson-1C changes;
Patch (3/3):
- Rename LS1C_RTC_CTRL_WORKAROUND to LOONGSON_RTC_CTRL_WORKAROUND for
consistency.
Link to V1:
https://lore.kernel.org/all/cover.1766471839.git.zhoubinbin@loongson.cn/
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
.../devicetree/bindings/rtc/loongson,rtc.yaml | 13 ++++
drivers/rtc/rtc-loongson.c | 71 ++++++++++++-------
2 files changed, 60 insertions(+), 24 deletions(-)
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
--
2.47.3
next reply other threads:[~2026-01-17 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 2:26 Binbin Zhou [this message]
2026-01-17 2:26 ` [PATCH v3 1/3] dt-bindings: rtc: loongson: Correct Loongson-1C interrupts property Binbin Zhou
2026-01-19 18:24 ` Conor Dooley
2026-01-20 7:50 ` Alexandre Belloni
2026-01-20 19:24 ` Conor Dooley
2026-01-20 22:49 ` Alexandre Belloni
2026-01-20 23:39 ` Conor Dooley
2026-01-21 6:52 ` Binbin Zhou
2026-01-21 18:28 ` Conor Dooley
2026-01-17 2:26 ` [PATCH v3 2/3] dt-bindings: rtc: loongson: Document Loongson-2K0300 compatible Binbin Zhou
2026-01-19 18:21 ` Conor Dooley
2026-01-17 2:26 ` [PATCH v3 3/3] rtc: loongson: Add Loongson-2K0300 support Binbin Zhou
2026-01-30 23:16 ` [PATCH v3 0/3] RTC: " 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=cover.1768616276.git.zhoubinbin@loongson.cn \
--to=zhoubinbin@loongson.cn \
--cc=alexandre.belloni@bootlin.com \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maoxiaochuan@loongson.cn \
--cc=robh@kernel.org \
--cc=zhoubb.aaron@gmail.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