[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5373C589.9080405@gmail.com>
Date: Wed, 14 May 2014 21:35:37 +0200
From: Tomasz Figa <tomasz.figa@...il.com>
To: Chanwoo Choi <cw00.choi@...sung.com>, kgene.kim@...sung.com,
t.figa@...sung.com
CC: linux-kernel@...r.kernel.org, linux@....linux.org.uk,
ben-linux@...ff.org, arnd@...db.de, olof@...om.net,
marc.zyngier@....com, thomas.abraham@...aro.org,
kyungmin.park@...sung.com, inki.dae@...sung.com,
sw0312.kim@...sung.com, hyunhee.kim@...sung.com,
yj44.cho@...sung.com, chanho61.park@...sung.com,
sajjan.linux@...il.com, tushar.behera@...aro.org,
sachin.kamat@...aro.org, linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Mike Turquette <mturquette@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCHv5 4/5] dt-bindings: add documentation for Exynos3250 clock
controller
Hi,
On 13.05.2014 15:05, Chanwoo Choi wrote:
> The Exynos3250 clocks are statically listed and registered using the
> Samsung specific common clock helper functions. Both device tree based
> clock lookup and clkdev based clock lookups are supported.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@...sung.com>
> Signed-off-by: Tomasz Figa <t.figa@...sung.com>
> Acked-by: Kyungmin Park <kyungmin.park@...sung.com>
> Cc: Mike Turquette <mturquette@...aro.org>
> Cc: Kukjin Kim <kgene.kim@...sung.com>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Pawel Moll <pawel.moll@....com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Ian Campbell <ijc+devicetree@...lion.org.uk>
> Cc: Kumar Gala <galak@...eaurora.org>
> Cc: Randy Dunlap <rdunlap@...radead.org>
> Cc: Tomasz Figa <t.figa@...sung.com>
> ---
> .../devicetree/bindings/clock/exynos3250-clock.txt | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/exynos3250-clock.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/exynos3250-clock.txt b/Documentation/devicetree/bindings/clock/exynos3250-clock.txt
> new file mode 100644
> index 0000000..aadc9c5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/exynos3250-clock.txt
> @@ -0,0 +1,41 @@
> +* Samsung Exynos3250 Clock Controller
> +
> +The Exynos3250 clock controller generates and supplies clock to various
> +controllers within the Exynos3250 SoC.
> +
> +Required Properties:
> +
> +- compatible: should be one of the following.
> + - "samsung,exynos3250-cmu" - controller compatible with Exynos3250 SoC.
> +
> +- reg: physical base address of the controller and length of memory mapped
> + region.
> +
> +- #clock-cells: should be 1.
> +
> +Each clock is assigned an identifier and client nodes can use this identifier
> +to specify the clock which they consume.
> +
> +All available clocks are defined as preprocessor macros in
> +dt-bindings/clock/exynos3250.h header and can be used in device
> +tree sources.
> +
> +Example 1: An example of a clock controller node is listed below.
> +
> + cmu: clock-controller@...30000 {
> + compatible = "samsung,exynos3250-cmu";
> + reg = <0x10030000 0x20000>;
> + #clock-cells = <1>;
> + };
> +
> +Example 2: UART controller node that consumes the clock generated by the clock
> + controller. Refer to the standard clock bindings for information
> + about 'clocks' and 'clock-names' property.
> +
> + serial@...00000 {
> + compatible = "samsung,exynos4210-uart";
> + reg = <0x13800000 0x100>;
> + interrupts = <0 109 0>;
> + clocks = <&cmu CLK_UART0>, <&cmu CLK_SCLK_UART0>;
> + clock-names = "uart", "clk_uart_baud0";
> + };
>
Oops, I've forgotten to apply this one. Since it doesn't have any
dependencies, Kukjin, could you apply it on top of my pull requests with
my Ack? Thanks in advance.
Acked-by: Tomasz Figa <t.figa@...sung.com>
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists