devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: WANG Xuerui <git@xen0n.name>
To: linux-rtc@vger.kernel.org
Cc: WANG Xuerui <git@xen0n.name>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH RESEND v5 0/6] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC
Date: Tue, 24 Aug 2021 00:31:36 +0800	[thread overview]
Message-ID: <20210823163142.586529-1-git@xen0n.name> (raw)

I'm resending the series after waiting for seven rc's without any response;
did I overlook any submission procedure? Rebased against current rtc-next
and tweaked Cc's for this submission, though.

This is all compiled and tested on a 3A4000 box, as usual. 3A3000+7A and
2K systems are tested previously, and these should not be affected. (To
Loongson employees reading this: please test on your rigs and give
feedback, for getting this done before the next merge window!)

While we're at it, I'd like to know which tree should this series go in via;
is it rtc-next or mips-next? I'd prefer mips-next, since the last 4 patches
all deal with MIPS things.


Original cover letter:

This patch series adds support for the RTC module found on various
Loongson systems with the Loongson-2K SoC or the LS7A bridge chip.
The driver is rewritten from an out-of-tree version to meet mainline
standards. I write kernel code as a hobby, though, so there might still
be overlooked issues. Any suggestions are welcome.

v5:
- Minor changes per Nobuhiro-san's review
  - Simplified one register-write-and-return
  - Explicitly depend on OF, remove of_match_ptr usage for now
- Tested on Loongson-3A4000; 2K should work too because there's no
  functional change either

v4:
- Rebased on top of next-20210628
- Added Jiaxun's Tested-by tag for Loongson-2K; no functional changes
- Addressed all review comments from v3
  - Rewritten field operations with FIELD_GET/FIELD_PREP
  - Removed all error logs
  - Removed unnecessary spinlocking (RTC core already protects against
    concurrent device file operations)

v3:
- Fixed compile error not discovered after rebase (blame sleep
  deprivation)
- Tested on Loongson-3A4000 and Loongson-2K

v2:
- Rebased on top of latest linux-next
- Updated Huacai's e-mail address to the kernel.org one
- Added collected tags
- Added adaptation for newly upstreamed Loongson-2K platforms

WANG Xuerui (6):
  rtc: ls2x: Add support for the Loongson-2K/LS7A RTC
  dt-bindings: rtc: Add bindings for LS2X RTC
  MIPS: Loongson64: DTS: Add RTC support to LS7A
  MIPS: Loongson: Enable LS2X RTC in loongson3_defconfig
  MIPS: Loongson64: DTS: Add RTC support to Loongson-2K
  MIPS: Loongson: Enable LS2X RTC in loongson2k_defconfig

 .../devicetree/bindings/rtc/trivial-rtc.yaml  |   2 +
 .../boot/dts/loongson/loongson64-2k1000.dtsi  |   5 +
 arch/mips/boot/dts/loongson/ls7a-pch.dtsi     |   5 +
 arch/mips/configs/loongson2k_defconfig        |   1 +
 arch/mips/configs/loongson3_defconfig         |   1 +
 drivers/rtc/Kconfig                           |  11 ++
 drivers/rtc/Makefile                          |   1 +
 drivers/rtc/rtc-ls2x.c                        | 180 ++++++++++++++++++
 8 files changed, 206 insertions(+)
 create mode 100644 drivers/rtc/rtc-ls2x.c


base-commit: 8158da6a33f2656c2a98c30eb9185a44e215a6b6
-- 
2.33.0


             reply	other threads:[~2021-08-23 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 16:31 WANG Xuerui [this message]
2021-08-23 16:31 ` [PATCH RESEND v5 1/6] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC WANG Xuerui
2021-08-31  0:33   ` Nobuhiro Iwamatsu
2021-09-25 22:14   ` Alexandre Belloni
2021-09-27 11:16   ` Alexandre Belloni
2021-08-23 16:31 ` [PATCH RESEND v5 2/6] dt-bindings: rtc: Add bindings for LS2X RTC WANG Xuerui
2021-08-23 16:31 ` [PATCH RESEND v5 3/6] MIPS: Loongson64: DTS: Add RTC support to LS7A WANG Xuerui
2021-08-23 16:31 ` [PATCH RESEND v5 5/6] MIPS: Loongson64: DTS: Add RTC support to Loongson-2K WANG Xuerui

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=20210823163142.586529-1-git@xen0n.name \
    --to=git@xen0n.name \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mips@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).