devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Dave Gerlach <d-gerlach@ti.com>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <bcousson@baylibre.com>
Subject: Re: [PATCH] ARM: dts: am43xx-clocks: use ti,fixed-factor-clock for dpll_per_clkdcoldo
Date: Mon, 19 May 2014 15:25:16 +0300	[thread overview]
Message-ID: <5379F82C.3020702@ti.com> (raw)
In-Reply-To: <1396040071-17900-1-git-send-email-d-gerlach@ti.com>

On 03/28/2014 10:54 PM, Dave Gerlach wrote:
> Use the ti,fixed-factor-clock version so that autoidle for
> dpll_per_clkdcoldo is properly controlled after power management code
> is introduced. Without this the clock may be held active even when
> it is gated.
>
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>

Thanks, queued for 3.16/clk-dt.

> ---
>   arch/arm/boot/dts/am43xx-clocks.dtsi | 9 ++++++---
>   1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/am43xx-clocks.dtsi b/arch/arm/boot/dts/am43xx-clocks.dtsi
> index 142009c..1d9b6bb 100644
> --- a/arch/arm/boot/dts/am43xx-clocks.dtsi
> +++ b/arch/arm/boot/dts/am43xx-clocks.dtsi
> @@ -609,10 +609,13 @@
>
>   	dpll_per_clkdcoldo: dpll_per_clkdcoldo {
>   		#clock-cells = <0>;
> -		compatible = "fixed-factor-clock";
> +		compatible = "ti,fixed-factor-clock";
>   		clocks = <&dpll_per_ck>;
> -		clock-mult = <1>;
> -		clock-div = <1>;
> +		ti,clock-mult = <1>;
> +		ti,clock-div = <1>;
> +		ti,autoidle-shift = <8>;
> +		reg = <0x2e14>;
> +		ti,invert-autoidle-bit;
>   	};
>
>   	dll_aging_clk_div: dll_aging_clk_div {
>


      reply	other threads:[~2014-05-19 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 20:54 [PATCH] ARM: dts: am43xx-clocks: use ti,fixed-factor-clock for dpll_per_clkdcoldo Dave Gerlach
2014-05-19 12:25 ` Tero Kristo [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=5379F82C.3020702@ti.com \
    --to=t-kristo@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).