From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH V2 0/2] rtc: Introduce rtc-ti-k3
Date: Tue, 10 May 2022 19:25:57 -0500 [thread overview]
Message-ID: <20220511002600.27964-1-nm@ti.com> (raw)
Hi,
This series adds support for TI K3 RTC as instantiated on TI's AM625
SoC.
Documentation in the current early release version of Technical
Reference Manual is incomplete at the moment, but due to be updated
later this year.
https://www.ti.com/lit/pdf/spruiv7
Testing log can be found here (next-20220509 + additional node for dts):
https://gist.github.com/nmenon/df536a01c3c14cf8b6c809aec8972339
Changes since V1:
* bindings updated for review comments
* driver modified to move to regmap fields and review comments
incorporated.
V1: https://lore.kernel.org/all/20220412073138.25027-1-nm@ti.com/
Nishanth Menon (2):
dt-bindings: rtc: Add TI K3 RTC description
rtc: Introduce ti-k3-rtc
.../devicetree/bindings/rtc/ti,k3-rtc.yaml | 61 ++
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-ti-k3.c | 688 ++++++++++++++++++
4 files changed, 761 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/ti,k3-rtc.yaml
create mode 100644 drivers/rtc/rtc-ti-k3.c
--
2.31.1
next reply other threads:[~2022-05-11 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 0:25 Nishanth Menon [this message]
2022-05-11 0:25 ` [PATCH V2 1/2] dt-bindings: rtc: Add TI K3 RTC description Nishanth Menon
2022-05-11 16:28 ` Krzysztof Kozlowski
2022-05-11 19:38 ` Nishanth Menon
2022-05-12 10:12 ` Krzysztof Kozlowski
2022-05-11 0:25 ` [PATCH V2 2/2] rtc: Introduce ti-k3-rtc Nishanth Menon
2022-05-11 0:52 ` Andrew Davis
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=20220511002600.27964-1-nm@ti.com \
--to=nm@ti.com \
--cc=a.zummo@towertech.it \
--cc=afd@ti.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).