From: Javier Carrasco <javier.carrasco@wolfvision.net>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: rtc: nxp,pcf8563: add hiz-output property
Date: Tue, 30 Jan 2024 22:34:24 +0100 [thread overview]
Message-ID: <e8ae1f05-fe57-4fec-9e7e-1fccaed171e6@wolfvision.net> (raw)
In-Reply-To: <202310260956166bdcb845@mail.local>
Hello Alexandre,
On 26.10.23 11:56, Alexandre Belloni wrote:
> There is a pin named INTA, it can mux 4 different functions:
>
> - clock output
> - battery mode indication
> - interrupt
> - HiZ
>
> with pinmuxing, you can select which function you want for the pin. I'm
> not sure what is misused there.
>
> Can you explain what is your actual use case? I'm starting to understand
> that what you want is simply disable clock out because you are not using
> the interrupt.
>
> If we assume we are never going to use battery mode, then we could
> simply used the CCF for this like the other RTC drivers.
>
Could you please point me to an RTC driver that uses the CCF for a
similar application? I am not sure what you mean with the battery mode
to make use of the HiZ, and I would like to push forward with this
functionality.
Thank you.
Best regards,
Javier Carrasco
prev parent reply other threads:[~2024-01-30 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 16:21 [PATCH 0/2] rtc: pcf85363: add support for high-impedance output Javier Carrasco
2023-10-25 16:21 ` [PATCH 1/2] " 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 [this message]
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=e8ae1f05-fe57-4fec-9e7e-1fccaed171e6@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).