From: Antoni Pokusinski <apokusinski01@gmail.com>
To: alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org,
alexander.stein@ew.tq-group.com
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Antoni Pokusinski <apokusinski01@gmail.com>
Subject: [PATCH v3 0/3] add support for RV8063 SPI rtc
Date: Thu, 10 Apr 2025 22:23:14 +0200 [thread overview]
Message-ID: <20250410202317.25873-1-apokusinski01@gmail.com> (raw)
This patch series adds support for the Microcrystal RV8063 real time
clock module with SPI interface. This device is very similar to RV8263
(which however uses I2C), so I decided to extend the existing driver instead
of creating a new one.
RV8063 datasheet: https://www.microcrystal.com/fileadmin/Media/Products/RTC/App.Manual/RV-8063-C7_App-Manual.pdf
---
Changes since v2:
* dt-binding: send as patch 1/3, not patch 3/3
* dt-binding: fix indentation in spi example
* dt-binding: fix order of enums: rv8063 before rv8263
Changes since v1:
* pcf85063 driver: drop MODULE_ALIAS, add id_table
* dt-binding: add "pcf85063" to the commit message
Antoni Pokusinski (3):
dt-bindings: rtc: pcf85063: add binding for RV8063
rtc: pcf85063: create pcf85063_i2c_probe
rtc: pcf85063: add support for RV8063
.../devicetree/bindings/rtc/nxp,pcf85063.yaml | 33 +++-
drivers/rtc/Kconfig | 21 ++-
drivers/rtc/rtc-pcf85063.c | 175 +++++++++++++++---
3 files changed, 192 insertions(+), 37 deletions(-)
--
2.25.1
next reply other threads:[~2025-04-10 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 20:23 Antoni Pokusinski [this message]
2025-04-10 20:23 ` [PATCH v3 1/3] dt-bindings: rtc: pcf85063: add binding for RV8063 Antoni Pokusinski
2025-04-11 19:27 ` Rob Herring
2025-04-10 20:23 ` [PATCH v3 2/3] rtc: pcf85063: create pcf85063_i2c_probe Antoni Pokusinski
2025-04-10 20:23 ` [PATCH v3 3/3] rtc: pcf85063: add support for RV8063 Antoni Pokusinski
2025-04-11 19:24 ` Rob Herring
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=20250410202317.25873-1-apokusinski01@gmail.com \
--to=apokusinski01@gmail.com \
--cc=alexander.stein@ew.tq-group.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.