linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5
Date: Sat, 17 May 2014 01:24:15 +0200	[thread overview]
Message-ID: <53769E1F.1090706@gmail.com> (raw)
In-Reply-To: <1400029876-5830-5-git-send-email-thomas.ab@samsung.com>

Hi Thomas,

Please see my comments inline.

On 14.05.2014 03:11, Thomas Abraham wrote:
> From; Thomas Abraham <thomas.ab@samsung.com>
> 
> The clock blocks within the CMU_CPU clock domain are put together into a
> new composite clock type called the cpu clock. This clock type requires
> configuration data that will be atomically programmed in the multiple
> clock blocks encapsulated within the cpu clock type when the parent clock
> frequency is changed. This configuration data is held in the clock controller
> node. Update clock binding documentation about this configuration data format
> for Samsung Exynos4 and Exynos5 platforms.
> 
> Cc: Tomasz Figa <t.figa@samsung.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Pawel Moll <pawel.moll@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> Cc: Kumar Gala <galak@codeaurora.org>
> Cc: <devicetree@vger.kernel.org>
> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
> ---
>  .../devicetree/bindings/clock/exynos4-clock.txt    |   37 ++++++++++++++++++++
>  .../devicetree/bindings/clock/exynos5250-clock.txt |   36 +++++++++++++++++++
>  2 files changed, 73 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/exynos4-clock.txt b/Documentation/devicetree/bindings/clock/exynos4-clock.txt
> index f5a5b19..0934e02 100644
> --- a/Documentation/devicetree/bindings/clock/exynos4-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/exynos4-clock.txt
> @@ -15,6 +15,35 @@ Required Properties:
>  
>  - #clock-cells: should be 1.
>  
> +- samsung,armclk-divider-table: when the frequency of the APLL is changed
> +  the divider clocks in CMU_CPU clock domain also need to be updated. These
> +  divider clocks have SoC specific divider clock output requirements for a
> +  specific APLL clock speeds. When APLL clock rate is changed, these divider
> +  clocks are reprogrammed with pre-determined values in order to maintain the
> +  SoC specific divider clock outputs. This property lists the divider values
> +  for divider clocks in the CMU_CPU block for supported APLL clock speeds.
> +  The format of each entry included in the arm-frequency-table should be
> +  as defined below

As far as I understand, the relation is not between the APLL frequency
and particular clocks in CPU domain, but rather between the latter and
input clock to CPU domain, which is _after_ the two dividers (called
DIV_CORE and DIV_CORE2 or ARM_DIV1 and ARM_DIV2), which is also exactly
the output frequency of ARMCLK.

> +
> +  - for Exynos4210 and Exynos4212 based platforms:
> +      cell #1: arm clock parent frequency

Considering my comment above, this should be rather ARMCLK frequency.

> +      cell #2 ~ cell 9#: value of clock divider in the following order
> +	        corem0_ratio, corem1_ratio, periph_ratio, atb_ratio,
> +		pclk_dbg_ratio, apll_ratio, copy_ratio, hpm_ratio.
> +
> +  - for Exynos4412 based platforms:
> +      cell #1: expected arm clock parent frequency

Ditto.

> +      cell #2 ~ cell #10: value of clock divider in the following order
> +	       corem0_ratio, corem1_ratio, periph_ratio, atb_ratio,
> +               pclk_dbg_ratio, apll_ratio, copy_ratio, hpm_ratio, cores_ratio
> +
> +- samsung,armclk-cells: defines the number of cells in
> +  samsung,armclk-divider-table property. The value of this property depends on
> +  the SoC type.

To follow conventions used by all other bindings with variable number of
cells, the property should be called "#samsung,armclk-cells". AFAIK the
"#" should be interpreted as "number of" and so accents the meaning of
the property.

> +
> +  - for Exynos4210 and Exynos4212: the value should be 9.
> +  - for Exynos4412: the value should be 10.
> +
>  Each clock is assigned an identifier and client nodes can use this identifier
>  to specify the clock which they consume.
>  
> @@ -28,6 +57,14 @@ Example 1: An example of a clock controller node is listed below.
>  		compatible = "samsung,exynos4210-clock";
>  		reg = <0x10030000 0x20000>;
>  		#clock-cells = <1>;
> +
> +		samsung,armclk-cells = <9>;
> +		samsung,armclk-divider-table = <1200000 3 7 3 4 1 7 5 0>,
> +					       <1000000 3 7 3 4 1 7 4 0>,
> +					       < 800000 3 7 3 3 1 7 3 0>,
> +					       < 500000 3 7 3 3 1 7 3 0>,
> +					       < 400000 3 7 3 3 1 7 3 0>,
> +					       < 200000 1 3 1 1 1 0 3 0>;
>  	};
>  
>  Example 2: UART controller node that consumes the clock generated by the clock
> diff --git a/Documentation/devicetree/bindings/clock/exynos5250-clock.txt b/Documentation/devicetree/bindings/clock/exynos5250-clock.txt
> index 536eacd..3d63d09 100644
> --- a/Documentation/devicetree/bindings/clock/exynos5250-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/exynos5250-clock.txt
> @@ -13,6 +13,24 @@ Required Properties:

Same comments apply to this file as well.

Also, shouldn't you also extend exynos5420-clock.txt in the same way?

Best regards,
Tomasz

  reply	other threads:[~2014-05-16 23:24 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14  1:11 [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms Thomas Abraham
2014-05-14  1:11 ` [PATCH v4 1/8] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies Thomas Abraham
2014-05-14  3:46   ` Viresh Kumar
2014-05-14  6:17     ` Lukasz Majewski
2014-05-14  6:20       ` Viresh Kumar
2014-05-14 13:43         ` Thomas Abraham
2014-05-14 13:50           ` Viresh Kumar
2014-05-14 14:18             ` Thomas Abraham
2014-05-14 14:20               ` Viresh Kumar
2014-05-14  1:11 ` [PATCH v4 2/8] clk: samsung: change scope of samsung clock lock to global Thomas Abraham
2014-05-14  3:50   ` Viresh Kumar
2014-05-14 13:26     ` Thomas Abraham
2014-05-16 12:30   ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 3/8] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-05-15 18:18   ` Doug Anderson
2014-05-15 19:17     ` Heiko Stübner
2014-05-15 19:36       ` Doug Anderson
2014-05-15 20:12         ` Heiko Stübner
2014-05-15 20:26           ` Doug Anderson
2014-05-16  4:55             ` Thomas Abraham
2014-05-16 17:17   ` Tomasz Figa
2014-05-23 14:41     ` Thomas Abraham
2014-05-23 14:50       ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 4/8] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5 Thomas Abraham
2014-05-16 23:24   ` Tomasz Figa [this message]
2014-05-17  0:00     ` Tomasz Figa
2014-05-26  6:05     ` Thomas Abraham
2014-05-26 11:02       ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 5/8] clk: exynos: use cpu-clock provider type to represent arm clock Thomas Abraham
2014-05-14 21:37   ` Mike Turquette
2014-05-15  7:48     ` Thomas Abraham
2014-05-15  8:10       ` Lukasz Majewski
2014-05-15  9:59         ` Thomas Abraham
2014-05-16  5:14     ` Thomas Abraham
2014-05-16 23:57   ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 6/8] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data Thomas Abraham
2014-05-16 23:16   ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 7/8] ARM: Exynos: switch to using generic cpufreq-cpu0 driver Thomas Abraham
2014-05-14 12:50   ` Arnd Bergmann
2014-05-14 13:05     ` Viresh Kumar
2014-05-14 13:11       ` Heiko Stübner
2014-05-14 13:14         ` Viresh Kumar
2014-05-14 13:18           ` Arnd Bergmann
2014-05-14 13:45             ` Rob Herring
2014-05-14 14:33               ` Arnd Bergmann
2014-07-08  5:15                 ` Viresh Kumar
2014-05-14 14:03         ` Thomas Abraham
2014-05-14 14:09           ` Sudeep Holla
2014-05-14 14:09     ` Thomas Abraham
2014-05-17  0:04   ` Tomasz Figa
2014-05-14  1:11 ` [PATCH v4 8/8] cpufreq: exynos: remove all exynos specific cpufreq driver support Thomas Abraham
2014-05-14  3:57   ` Viresh Kumar
2014-05-14  7:20   ` Lukasz Majewski
2014-05-14 13:53     ` Thomas Abraham
2014-05-14 12:51 ` [PATCH v4 0/8] cpufreq: use cpufreq-cpu0 driver for exynos based platforms Arnd Bergmann
2014-05-14 13:07   ` Viresh Kumar
2014-05-14 13:16     ` Arnd Bergmann
2014-05-17  0:14 ` Tomasz Figa

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=53769E1F.1090706@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).