From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
<linux-clk@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-snps-arc@lists.infradead.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH RESEND] CLK: ARC: Set initial pll output frequency specified in device tree
Date: Tue, 14 Nov 2017 19:01:28 +0200 [thread overview]
Message-ID: <1b07abf9-c94d-1759-4182-519b77c8bb37@mentor.com> (raw)
In-Reply-To: <20171114122020.9800-1-Eugeniy.Paltsev@synopsys.com>
On 11/14/2017 02:20 PM, Eugeniy Paltsev wrote:
> Add option to set initial output frequency of plls via
> "clock-frequency" property in pll's device tree node.
> This frequency will be set while pll driver probed.
>
> The usage example is setting CPU clock frequency on boot
> See discussion:
> https://www.mail-archive.com/linux-snps-arc@lists.infradead.org/msg02689.html
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> ---
> .../bindings/clock/snps,hsdk-pll-clock.txt | 5 ++++
> .../devicetree/bindings/clock/snps,pll-clock.txt | 5 ++++
> drivers/clk/axs10x/pll_clock.c | 34 ++++++++++++++++++++--
> drivers/clk/clk-hsdk-pll.c | 34 ++++++++++++++++++++--
> 4 files changed, 74 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/snps,hsdk-pll-clock.txt b/Documentation/devicetree/bindings/clock/snps,hsdk-pll-clock.txt
> index c56c755..5703059 100644
> --- a/Documentation/devicetree/bindings/clock/snps,hsdk-pll-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/snps,hsdk-pll-clock.txt
> @@ -13,6 +13,10 @@ Required properties:
> - clocks: shall be the input parent clock phandle for the PLL.
> - #clock-cells: from common clock binding; Should always be set to 0.
>
> +Optional properties:
> +- clock-frequency: output frequency generated by pll in Hz which will be set
> +while probing. Should be a single cell.
> +
> Example:
> input_clk: input-clk {
> clock-frequency = <33333333>;
> @@ -25,4 +29,5 @@ Example:
> reg = <0x00 0x10>;
> #clock-cells = <0>;
> clocks = <&input_clk>;
> + clock-frequency = <1000000000>;
> };
> diff --git a/Documentation/devicetree/bindings/clock/snps,pll-clock.txt b/Documentation/devicetree/bindings/clock/snps,pll-clock.txt
> index 11fe487..5908f99 100644
> --- a/Documentation/devicetree/bindings/clock/snps,pll-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/snps,pll-clock.txt
> @@ -13,6 +13,10 @@ registers and second for corresponding LOCK CGU register.
> - clocks: shall be the input parent clock phandle for the PLL.
> - #clock-cells: from common clock binding; Should always be set to 0.
>
> +Optional properties:
> +- clock-frequency: output frequency generated by pll in Hz which will be set
> +while probing. Should be a single cell.
> +
> Example:
> input-clk: input-clk {
> clock-frequency = <33333333>;
> @@ -25,4 +29,5 @@ Example:
> reg = <0x80 0x10>, <0x100 0x10>;
> #clock-cells = <0>;
> clocks = <&input-clk>;
> + clock-frequency = <100000000>;
> };
You may check Documentation/devicetree/bindings/clock/clock-bindings.txt
about how to assign initial clock rates, in general 'clock-frequency'
property is a property of clock consumers with two exceptions of simple
clock sources, namely it is used in fixed clock and PWM clock bindings.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2017-11-14 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 12:20 Eugeniy Paltsev
2017-11-14 17:01 ` Vladimir Zapolskiy [this message]
2017-11-14 21:19 ` Alexey Brodkin
2017-11-14 23:46 ` sboyd
2017-12-09 13:50 ` Eugeniy Paltsev
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=1b07abf9-c94d-1759-4182-519b77c8bb37@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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®