From: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
To: alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org
Cc: skhan@linuxfoundation.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
akhileshpatilvnit@gmail.com
Subject: [PATCH 0/7] rtc: m41t93: add new features alarm, clock out, watchdog
Date: Wed, 3 Sep 2025 19:53:49 +0530 [thread overview]
Message-ID: <cover.1756908788.git.akhilesh@ee.iitb.ac.in> (raw)
This patch series adds following to m41t93 rtc driver.
Functionalities:
- Alarm support (support to configure alarm 1)
- Square wave output support
- Watchdog support
Code improvements:
this series migrates existing driver to use standard regmap interface
for spi instead of direct spi calls and uses regmap for new features.
Bug fix:
Fixes device probe issue after power-on due to incorrect assumptions of
reset values of the registers.
Device tree support:
Adds device tree support to the driver along with binding documentation.
Testing:
This patch series is validated on TI am62x board with m41t93 rtc chip
connected to spi0 bus.
regmap migration is additionally tested by observing spi transfers
with the help of logic analyzer. Short summary of test flow is added in
commit message of respective features.
Datasheet:
https://www.st.com/resource/en/datasheet/m41t93.pdf
patch 4 to 7 depend on patch 3 (regmap patch)
Regards,
Akhilesh
Akhilesh Patil (7):
rtc: m41t93: add device tree support
dt-bindings: rtc: add bindings for m41t93
rtc: m41t93: migrate to regmap api for register access
rtc: m41t93: Add alarm support
rtc: m41t93: fix device connection/detection logic during probe
rtc: m41t93: Add square wave clock provider support
rtc: m41t93: Add watchdog support
.../devicetree/bindings/rtc/st,m41t93.yaml | 43 ++
drivers/rtc/rtc-m41t93.c | 489 ++++++++++++++++--
2 files changed, 479 insertions(+), 53 deletions(-)
create mode 100644 Documentation/devicetree/bindings/rtc/st,m41t93.yaml
--
2.34.1
next reply other threads:[~2025-09-03 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:23 Akhilesh Patil [this message]
2025-09-03 14:25 ` [PATCH 1/7] rtc: m41t93: add device tree support Akhilesh Patil
2025-09-03 14:25 ` [PATCH 2/7] dt-bindings: rtc: add bindings for m41t93 Akhilesh Patil
2025-09-03 14:30 ` Krzysztof Kozlowski
2025-09-03 20:33 ` Rob Herring (Arm)
2025-09-03 14:26 ` [PATCH 3/7] rtc: m41t93: migrate to regmap api for register access Akhilesh Patil
2025-09-03 14:26 ` [PATCH 4/7] rtc: m41t93: Add alarm support Akhilesh Patil
2025-09-04 5:07 ` kernel test robot
2025-09-03 14:27 ` [PATCH 5/7] rtc: m41t93: fix device connection/detection logic during probe Akhilesh Patil
2025-09-03 14:47 ` Alexandre Belloni
2025-09-03 14:27 ` [PATCH 6/7] rtc: m41t93: Add square wave clock provider support Akhilesh Patil
2025-09-04 4:42 ` kernel test robot
2025-09-03 14:28 ` [PATCH 7/7] rtc: m41t93: Add watchdog support Akhilesh Patil
2025-09-04 23:23 ` kernel test robot
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.1756908788.git.akhilesh@ee.iitb.ac.in \
--to=akhilesh@ee.iitb.ac.in \
--cc=akhileshpatilvnit@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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).