mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: takasi-y@ops.dti.ne.jp
Cc: SH-Linux <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	ben.dooks@codethink.co.uk,
	Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>,
	devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
	Paul Mundt <lethal@linux-sh.org>,
	Mike Turquette <mturquette@linaro.org>,
	linux-kernel@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Date: Tue, 24 Sep 2013 13:52:15 +0900	[thread overview]
Message-ID: <20130924045215.GE3619@verge.net.au> (raw)
In-Reply-To: <20130924131331.0e9a5f830f531655b2ea0ebe@ops.dti.ne.jp>

[ Cc Laurent ]

On Tue, Sep 24, 2013 at 01:13:31PM +0900, takasi-y@ops.dti.ne.jp wrote:
> Device tree clock binding document for EMMA Mobile EV2 SMU.
> Following nodes are defined to describe clock tree.
> - renesas,emev2-smu
> - renesas,emev2-smu-clkdiv
> - renesas,emev2-smu-gclk

I realise this has been entirely consistent in the past and
even as recently as Linus' pre v3.12-rc2 master branch.
However, after some recent discussion we are now trying to make our
compatibility strings consistently of the form renesas,<unit>-<soc>.

With this in mind I believe the strings should be:

- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2

To be honest I am not quite sure about the "-clkdiv" and "-gclk"
bits and I would appreciate some review from others.

I have CCed Laurent as he may have some advice to offer here.

> 
> These bindings are designed manually based on
>  19UH0037EJ1000_SMU : System Management Unit User's Manual
> 
> Signed-off-by: Takashi Yoshii <takashi.yoshii.zj@renesas.com>
> ---
>  .../devicetree/bindings/clock/emev2-clock.txt      | 99 ++++++++++++++++++++++
>  1 file changed, 99 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/clock/emev2-clock.txt
> 
> diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt b/Documentation/devicetree/bindings/clock/emev2-clock.txt
> new file mode 100644
> index 0000000..f8649eb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
> @@ -0,0 +1,99 @@
> +Device tree Clock bindings for Renesas EMMA Mobile EV2
> +
> +This binding uses the common clock binding.
> +
> +* SMU
> +System Management Unit described in user's manual R19UH0037EJ1000_SMU.
> +This is not a clock provider, but clocks under SMU depend on it.
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu"
> +- reg: Address and Size of SMU registers
> +
> +* SMU_CLKDIV
> +Function block with an input mux and a divider, which corresponds to
> +"Serial clock generator" in fig."Clock System Overview" of the manual,
> +and "xxx frequency division setting register" (XXXCLKDIV) registers.
> +This makes internal (neither input nor output) clock that is provided
> +to input of xxxGCLK block.
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu-clkdiv"
> +- reg: Byte offset from SMU base and Bit position in the register
> +- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
> +- #clock-cells: Should be <0>
> +
> +* SMU_GCLK
> +Clock gating node shown as "Clock stop processing block" in the
> +fig."Clock System Overview" of the manual.
> +Registers are "xxx clock gate control register" (XXXGCLKCTRL).
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu-gclk"
> +- reg: Byte offset from SMU base and Bit position in the register
> +- clocks: Input clock as described in clock-bindings.txt
> +- #clock-cells: Should be <0>
> +
> +Example of provider:
> +
> +usia_u0_sclkdiv: usia_u0_sclkdiv {
> +	compatible = "renesas,emev2-smu-clkdiv";
> +	reg = <0x610 0>;
> +	clocks = <&pll3_fo>, <&pll4_fo>, <&pll1_fo>, <&osc1_fo>;
> +	#clock-cells = <0>;
> +};
> +
> +usia_u0_sclk: usia_u0_sclk {
> +	compatible = "renesas,emev2-smu-gclk";
> +	reg = <0x4a0 1>;
> +	clocks = <&usia_u0_sclkdiv>;
> +	#clock-cells = <0>;
> +};
> +
> +Example of consumer:
> +
> +uart@e1020000 {
> +	compatible = "renesas,em-uart";
> +	reg = <0xe1020000 0x38>;
> +	interrupts = <0 8 0>;
> +	clocks = <&usia_u0_sclk>;
> +	clock-names = "sclk";
> +};
> +
> +Example of clock-tree description:
> +
> + This describes a clock path in the clock tree
> +  c32ki -> pll3_fo -> usia_u0_sclkdiv -> usia_u0_sclk
> +
> +smu {
> +	compatible = "renesas,emev2-smu";
> +	reg = <0xe0110000 0x10000>;
> +	#address-cells = <2>;
> +	#size-cells = <0>;
> +
> +	c32ki: c32ki {
> +		compatible = "fixed-clock";
> +		clock-frequency = <32768>;
> +		#clock-cells = <0>;
> +	};
> +	pll3_fo: pll3_fo {
> +		compatible = "fixed-factor-clock";
> +		clocks = <&c32ki>;
> +		clock-div = <1>;
> +		clock-mult = <7000>;
> +		#clock-cells = <0>;
> +	};
> +	usia_u0_sclkdiv: usia_u0_sclkdiv {
> +		compatible = "renesas,emev2-smu-clkdiv";
> +		reg = <0x610 0>;
> +		clocks = <&pll3_fo>;
> +		#clock-cells = <0>;
> +	};
> +	usia_u0_sclk: usia_u0_sclk {
> +		compatible = "renesas,emev2-smu-gclk";
> +		reg = <0x4a0 1>;
> +		clocks = <&usia_u0_sclkdiv>;
> +		#clock-cells = <0>;
> +	};
> +};
> +
> -- 
> 1.8.1.5
> 

  reply	other threads:[~2013-09-24  4:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  4:05 [PATCH 0/6] ARM: shmobile: kzm9d-reference: migrate to common clock framework with DT Takashi Yoshii
2013-09-24  4:09 ` [PATCH 1/6] clocksource: em_sti: convert to clk_prepare/unprepare takasi-y
2013-09-24  4:42   ` Simon Horman
2013-09-26 10:18     ` Daniel Lezcano
2013-10-03  2:30       ` Simon Horman
2013-09-30 15:25   ` Laurent Pinchart
2013-10-01  9:05   ` Magnus Damm
2013-09-24  4:10 ` [PATCH 2/6] serial8250-em: " takasi-y
2013-09-24  4:44   ` Simon Horman
2013-09-24 13:41     ` Greg Kroah-Hartman
2013-10-03  2:30       ` Simon Horman
2013-09-30 15:25   ` Laurent Pinchart
2013-10-01  9:07   ` Magnus Damm
2013-09-24  4:12 ` [PATCH 3/6] sh: clkfwk: Select sh-/common- clkfwk alternatively takasi-y
2013-09-30 18:40   ` Laurent Pinchart
2013-10-04  5:25     ` takasi-y
2013-10-01  9:30   ` Magnus Damm
2013-09-24  4:13 ` [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings takasi-y
2013-09-24  4:52   ` Simon Horman [this message]
2013-09-24  9:00     ` takashi.yoshii.zj
2013-10-01 11:36     ` Laurent Pinchart
2013-10-02  1:28       ` Simon Horman
2013-10-06 17:16       ` Takashi YOSHII
2013-09-24  4:15 ` [PATCH 5/6] clk: emev2: Add support for emev2 SMU clocks with DT takasi-y
2013-10-01  9:15   ` Magnus Damm
2013-10-01 12:27     ` Laurent Pinchart
2013-10-04  5:44     ` takasi-y
2013-09-24  4:17 ` [PATCH 6/6] ARM: shmobile: kzm9d-reference: Use common clock framework takasi-y
2013-09-24  4:55   ` Simon Horman
2013-10-01  9:23   ` Magnus Damm
2013-09-24  4:56 ` [PATCH 0/6] ARM: shmobile: kzm9d-reference: migrate to common clock framework with DT Simon Horman
2013-09-25  7:17 ` Kuninori Morimoto
2013-10-04  1:12   ` takasi-y

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=20130924045215.GE3619@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ben.dooks@codethink.co.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@linaro.org \
    --cc=shinya.kuribayashi.px@renesas.com \
    --cc=takasi-y@ops.dti.ne.jp \
    /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®