From: Philipp Rosenberger <p.rosenberger@kunbus.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: "Lino Sanfilippo" <l.sanfilippo@kunbus.com>,
"Thomas Böhler" <t.boehler@kunbus.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
"Philipp Rosenberger" <p.rosenberger@kunbus.com>
Subject: [PATCH v3 0/2] rtc: pcf2127: make battery switch-over configurable
Date: Mon, 11 Nov 2024 16:41:42 +0100 [thread overview]
Message-ID: <20241111154144.163604-1-p.rosenberger@kunbus.com> (raw)
Hello,
This patch series adds the nxp,battery-backed device tree property to the
PCF2127 RTC driver. This flag indicates if the RTC is battery-backed, allowing
the driver to enable the battery switchover function if necessary.
Background
----------
The PCF2127 RTC driver currently supports the PCF2127, PCA2129, PCF2129, and
PCF2131 devices. Among these, only the newer PCF2131 has a different default
behavior for battery switchover: it is disabled by default, whereas it is
enabled on the other devices. If there is no firmware or bootloader setting
to enable battery switchover on the PCF2131, it will not automatically switch
to battery power, even if a battery is attached.
An alternative approach would be to enable battery switchover by default on
the PCF2131 without requiring a device tree property. However, this could be
undesirable, as it would make it impossible to disable battery
switchover.
Thank you.
Link [V2] https://patchwork.ozlabs.org/project/rtc-linux/list/?series=429144
Changes for V3:
- The nxp,battery-switch-over property was replaced with a boolean
nxp,battery-backed flag
- The register vales are not encoded in the device tree any more
- The driver enables battery switch-over in standard mode if the dt flag
is set.
Changes for V2:
- v1 was corrupted due to our company mail server settings. No functional
changes have been made; this version is identical to v1.
Philipp Rosenberger (2):
dt-bindings: rtc: pcf2127: Add nxp,battery-backed flag
rtc: pcf2127: Add 'nxp,battery-switchover' DT property to enable
battery switch-over
.../devicetree/bindings/rtc/nxp,pcf2127.yaml | 7 ++
drivers/rtc/rtc-pcf2127.c | 76 +++++++++++++++----
2 files changed, 68 insertions(+), 15 deletions(-)
--
2.39.5
next reply other threads:[~2024-11-11 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 15:41 Philipp Rosenberger [this message]
2024-11-11 15:41 ` [PATCH v3 1/2] dt-bindings: rtc: pcf2127: Add nxp,battery-backed flag Philipp Rosenberger
2024-11-12 16:40 ` Rob Herring
2024-11-11 15:41 ` [PATCH v3 2/2] rtc: pcf2127: Add 'nxp,battery-switchover' DT property to enable battery switch-over Philipp Rosenberger
2024-11-11 18:27 ` Christophe JAILLET
2024-11-12 16:38 ` Rob Herring
2024-11-14 8:51 ` [PATCH v3 0/2] rtc: pcf2127: make battery switch-over configurable Alexandre Belloni
2024-11-27 12:58 ` Philipp Rosenberger
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=20241111154144.163604-1-p.rosenberger@kunbus.com \
--to=p.rosenberger@kunbus.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hvilleneuve@dimonoff.com \
--cc=krzk+dt@kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=t.boehler@kunbus.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