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>,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v5 0/6] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC
Date: Fri,  2 Jul 2021 14:54:45 +0800	[thread overview]
Message-ID: <20210702065451.1175356-1-git@xen0n.name> (raw)

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.

This series is based on next-20210628, but should apply cleanly on rtc-next
too.

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: 3579aa488520feeda433ceca23ef4704bf8cd280
-- 
2.30.1


             reply	other threads:[~2021-07-02  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  6:54 WANG Xuerui [this message]
2021-07-02  6:54 ` [PATCH v5 1/6] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC WANG Xuerui
2021-07-02  6:54 ` [PATCH v5 2/6] dt-bindings: rtc: Add bindings for LS2X RTC WANG Xuerui
2021-07-02  6:54 ` [PATCH v5 3/6] MIPS: Loongson64: DTS: Add RTC support to LS7A WANG Xuerui
2021-07-02  6:54 ` [PATCH 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=20210702065451.1175356-1-git@xen0n.name \
    --to=git@xen0n.name \
    --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).