From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Cc: "linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: pcf85063: disable the clkout output by default
Date: Mon, 24 Aug 2026 09:58:16 +0000 [thread overview]
Message-ID: <2ce03d3b4cd9cce8e32fe1fe1ffbea5760bf9ef3.camel@siemens.com> (raw)
In-Reply-To: <20260824082456e0edd7c6@mail.local>
Hi Alexandre,
On Mon, 2026-08-24 at 10:24 +0200, Alexandre Belloni wrote:
> > From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> >
> > The PCF85063 powers up with its CLKOUT pin driving the 32.768 kHz. While
> > it's possible to request a specific default frequency in the DT via
> > assigned-clocks/assigned-clock-rates on the RTC node itself, even without
> > a real consumer referencing the clock, there is no such possibility to
> > disable the clock output by default.
>
> Are you sure about this? The CCF should disable the clock if it is not
> used.
There is late_initcall_sync(clk_disable_unused) (marked __init), but for the
clock providers registered later, say, via modules, there is no such mechanism.
And I double-checked this putting some debug prints into the driver,
nothing from struct clk_ops is being called without a consumer in DT.
> > Therefore gate CLKOUT in the driver before registering the OF provider,
> > mirroring the pcf8563 and hym8563 siblings which already force an off state
> > at registration. Doing it before devm_of_clk_add_hw_provider() leaves the
> > real consumers in the device tree free to re-enable the output afterwards,
> > while an otherwise unused CLKOUT now stays off.
> >
> > In practice it means that with CLKOUT disabled the RTC consumes around
> > 250nA at 25°C and 6-10uA with CLKOUT enabled (5v Vdd). Which means days vs
> > hours on a supercapacitor.
> >
> > Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> > ---
> > drivers/rtc/rtc-pcf85063.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
> > index 01e209d88f5f3..0b6d8083b6456 100644
> > --- a/drivers/rtc/rtc-pcf85063.c
> > +++ b/drivers/rtc/rtc-pcf85063.c
> > @@ -523,6 +523,12 @@ static struct clk *pcf85063_clkout_register_clk(struct pcf85063 *pcf85063)
> > /* optional override of the clockname */
> > of_property_read_string(node, "clock-output-names", &init.name);
> >
> > + /* power-on default is the 32768 Hz output on; gate it until claimed */
> > + ret = regmap_update_bits(pcf85063->regmap, PCF85063_REG_CTRL2,
> > + PCF85063_REG_CLKO_F_MASK, PCF85063_REG_CLKO_F_OFF);
> > + if (ret)
> > + return ret;
> > +
> > /* register the clock */
> > clk = devm_clk_register(&pcf85063->rtc->dev, &pcf85063->clkout_hw);
> >
> > --
> > 2.55.0
> >
--
Alexander Sverdlin
Siemens AG
www.siemens.com
prev parent reply other threads:[~2026-08-24 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:07 A. Sverdlin
2026-08-24 8:24 ` Alexandre Belloni
2026-08-24 9:58 ` Sverdlin, Alexander [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=2ce03d3b4cd9cce8e32fe1fe1ffbea5760bf9ef3.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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
all inboxes | Powered by JetHome®