From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Heiko Schocher <hs@denx.de>
Cc: linux-kernel@vger.kernel.org, Georg.Soffel@bosch-si.com,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4] rtc: pcf8563: add CLKOUT to common clock framework
Date: Sun, 18 Oct 2015 02:30:50 +0200 [thread overview]
Message-ID: <20151018003050.GZ3421@piout.net> (raw)
In-Reply-To: <1444995089-14493-1-git-send-email-hs@denx.de>
On 16/10/2015 at 13:31:29 +0200, Heiko Schocher wrote :
> Add the clkout output clk to the common clock framework.
> 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.
>
> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
>
> Changes in v4:
> - add comments from Alexandre Belloni
> - use devm_clk_register() instead of clk_register()
> - rework Documentation
>
> Changes in v3:
> - use CONFIG_COMMON_CLK for common clk framework
> changes
>
> Changes in v2:
> - add comments from Alexandre Belloni
> - remove the DT property, instead
> register for the CLKOUT a clk in the common
> clk framework. The clk is disabled by default.
>
> Documentation/devicetree/bindings/rtc/pcf8563.txt | 25 ++++
> drivers/rtc/rtc-pcf8563.c | 170 +++++++++++++++++++++-
> 2 files changed, 194 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/rtc/pcf8563.txt
>
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-18 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:31 Heiko Schocher
2015-10-18 0:30 ` Alexandre Belloni [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=20151018003050.GZ3421@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=Georg.Soffel@bosch-si.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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
all inboxes | Powered by JetHome®