From: Javier Carrasco <javier.carrasco@wolfvision.net>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Javier Carrasco <javier.carrasco@wolfvision.net>
Subject: [PATCH 0/2] rtc: pcf85363: add support for high-impedance output
Date: Wed, 25 Oct 2023 18:21:53 +0200 [thread overview]
Message-ID: <20231024-topic-pcf85363_hiz_output-v1-0-50908aff0e52@wolfvision.net> (raw)
This series adds support for the high-impedance (hi-Z) output mode. The
current implementation only allows two output modes: output clock
(default) and interrupt. In cases where the output is only used in
low-power modes as a clock source for other devices (PMU, PMIC, etc)
or the output is not needed at all, the hi-Z can be used to reduce power
consumption.
To model the hi-Z output, a new property "hiz-output" has been added and
the following cases have been taken into account:
- hiz-output = enabled: the output is not available in the design and
must be kept in high-impedance mode.
- hiz-output = sleep: the output is only required in sleep (low-power)
mode.
- hiz-output = disabled (default): for the sake of completion, this mode
ignores the hiz-output altogether and acts as if the property was not
defined.
Any other value will trigger a dev_warn and the default value (disabled)
will be used as it is done with other non-mandatory properties.
Signed-off-by: Javier Carrasco <javier.carrasco@wolfvision.net>
---
Javier Carrasco (2):
rtc: pcf85363: add support for high-impedance output
dt-bindings: rtc: nxp,pcf8563: add hiz-output property
.../devicetree/bindings/rtc/nxp,pcf85363.yaml | 14 +++++
drivers/rtc/rtc-pcf85363.c | 62 +++++++++++++++++++++-
2 files changed, 75 insertions(+), 1 deletion(-)
---
base-commit: cfb67623ce281e045ec11e3eddb1b68b879b53a1
change-id: 20231024-topic-pcf85363_hiz_output-d9c3c1f5ae59
Best regards,
--
Javier Carrasco <javier.carrasco@wolfvision.net>
next reply other threads:[~2023-10-25 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 16:21 Javier Carrasco [this message]
2023-10-25 16:21 ` [PATCH 1/2] rtc: pcf85363: add support for high-impedance output Javier Carrasco
2023-10-25 16:21 ` [PATCH 2/2] dt-bindings: rtc: nxp,pcf8563: add hiz-output property Javier Carrasco
2023-10-25 22:23 ` Alexandre Belloni
2023-10-25 22:30 ` Javier Carrasco
2023-10-25 23:23 ` Javier Carrasco
2023-10-26 0:50 ` Alexandre Belloni
2023-10-26 9:41 ` Javier Carrasco
2023-10-26 9:56 ` Alexandre Belloni
2023-10-26 10:13 ` Javier Carrasco
2023-10-26 10:21 ` Alexandre Belloni
2023-10-26 10:35 ` Javier Carrasco
2024-01-30 21:34 ` Javier Carrasco
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=20231024-topic-pcf85363_hiz_output-v1-0-50908aff0e52@wolfvision.net \
--to=javier.carrasco@wolfvision.net \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@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 read-only IMAP folder(s) and NNTP newsgroup(s).