From: Heiko Schocher <hs-ynQEQJNshbs@public.gmane.org>
To: Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Georg.Soffel-k21M0aUVSxZWk0Htik3J/w@public.gmane.org,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
Alessandro Zummo
<a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] rtc: pcf8563: disable CLKOUT
Date: Wed, 14 Oct 2015 06:19:29 +0200 [thread overview]
Message-ID: <561DD7D1.5040102@denx.de> (raw)
In-Reply-To: <20151013201703.GA3421-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
Hello Alexandre,
Am 13.10.2015 um 22:17 schrieb Alexandre Belloni:
> Hi,
>
> On 13/10/2015 at 07:08:58 +0200, Heiko Schocher wrote :
>> Disable the CLKOUT of the RTC after power-up.
>> After power-up/reset of the RTC, CLKOUT is enabled by default,
>> with CLKOUT enabled the RTC chip has 2-3 times higher power
>> consumption. If you do not need CLKOUT, you can disable the
>> CLKOUT with setting "disable-clkout" property.
>>
>
> I think you can simply unconditionally disable clkout. My preferred way
> of doing what you suggest is probably to register a clock in the CCF. If
> the clock is not used, it will be automatically disabled.
> It will also provide a generic way of setting the clkout frequency (some
> RTC are able to output 32kHZ, 1kHz and 1Hz).
Does disabling it ot break some boards?
I take a look into CCF, good idea.
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-10-14 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 5:08 [PATCH] rtc: pcf8563: disable CLKOUT Heiko Schocher
2015-10-13 20:17 ` Alexandre Belloni
[not found] ` <20151013201703.GA3421-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2015-10-14 4:19 ` Heiko Schocher [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=561DD7D1.5040102@denx.de \
--to=hs-ynqeqjnshbs@public.gmane.org \
--cc=Georg.Soffel-k21M0aUVSxZWk0Htik3J/w@public.gmane.org \
--cc=a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 NNTP newsgroup(s).