From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] clk: samsung: Document binding for Exynos4415 clock controller
Date: Fri, 24 Oct 2014 19:34:54 +0900 [thread overview]
Message-ID: <544A2B4E.8090604@samsung.com> (raw)
In-Reply-To: <544A2AA5.3020407@samsung.com>
Hi Sylwester,
On 10/24/2014 07:32 PM, Sylwester Nawrocki wrote:
> On 20/10/14 05:32, Chanwoo Choi wrote:
>> The Exynos4415 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.
>
> I think the above text is not relevant, DT binding is not supposed
> to depend on any OS. Instead I would just put here something like:
>
> "This patch adds DT binding documentation for Exynos4415 SoC system
> clock controllers."
OK, I will modify it as your comment.
>
>> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> Cc: Tomasz Figa <tomasz.figa@gmail.com>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>> ---
>> .../devicetree/bindings/clock/exynos4415-clock.txt | 49 ++++++++++++++++++++++
>> 1 file changed, 49 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/clock/exynos4415-clock.txt
>>
>> diff --git a/Documentation/devicetree/bindings/clock/exynos4415-clock.txt b/Documentation/devicetree/bindings/clock/exynos4415-clock.txt
>> new file mode 100644
>> index 0000000..8aa4f4f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/clock/exynos4415-clock.txt
>> @@ -0,0 +1,49 @@
>> +* Samsung Exynos4415 Clock Controller
>> +
>> +The Exynos4415 clock controller generates and supplies clock to various
>> +controllers within the Exynos4415 SoC.
>
> s/controllers/consumer devices/ ?
>
>> +
>> +Required Properties:
>
> s/P/p/ ?
I'll fix it.
>
>> +
>> +- compatible: should be one of the following.
>
> s/./:/ ?
I will change it (. -> :)
>
>> + - "samsung,exynos4415-cmu" - controller compatible with Exynos4415 SoC.
>
>>From current description it seems "samsung,exynos4415-cmu-dmc" is compatible
> with "samsung,exynos4415-cmu", which is not the case AFAIK.
> Perhaps we should change description here to something along the lines of:
>
> - "samsung,exynos4415-cmu" - for the main system clocks controller
> (CMU_LEFTBUS, CMU_RIGHTBUS, CMU_TOP, CMU_CPU clock domains),
>
>> + - "samsung,exynos4415-cmu-dmc" - controller compatible with
>> + Exynos4415 SoC for Dynamic Memory Controller domain.
>
> This seems unclear, how about
>
> - "samsung,exynos4415-cmu-dmc" - for the Exynos4415 SoC DRAM Memory
> Controller (DMC) domain clock controller.
>
> ?
OK, I'll modify it
>> +- 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/exynos4415.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 at 10030000 {
>> + compatible = "samsung,exynos4415-cmu";
>> + reg = <0x10030000 0x18000>;
>> + #clock-cells = <1>;
>> + };
>> +
>> + cmu-dmc: clock-controller at 105C0000 {
>> + compatible = "samsung,exynos4415-cmu-dmc";
>> + reg = <0x105C0000 0x3000>;
>> + #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_0: serial at 13800000 {
>> + 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";
>> + };
>
> I think we could omit those example snippets, it's all generic stuff and
> there is already plenty examples in descriptions of the DT binding for
> other SoCs.
OK, I'll drop this example.
Thanks for your review.
Best Regards,
Chanwoo Choi
>
> --
> Regards,
> Sylwester
>
next prev parent reply other threads:[~2014-10-24 10:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 3:29 [PATCH 0/5] Support new Exynos4415 SoC based on Cortex-A9 quad cores Chanwoo Choi
2014-10-20 3:32 ` [PATCH 1/5] ARM: EXYNOS: Add EXYNOS4415 SoC ID Chanwoo Choi
2014-10-24 11:43 ` Tomasz Figa
2014-10-24 11:46 ` Chanwoo Choi
2014-10-20 3:32 ` [PATCH 2/5] clk: samsung: exynos4415: Add clocks using common clock framework Chanwoo Choi
2014-10-24 10:54 ` Sylwester Nawrocki
2014-10-24 10:59 ` Chanwoo Choi
2014-10-24 13:18 ` Daniel Drake
2014-10-24 13:28 ` Tomasz Figa
2014-10-24 13:36 ` Chanwoo Choi
2014-10-24 13:56 ` Sylwester Nawrocki
2014-10-20 3:32 ` [PATCH 3/5] clk: samsung: Document binding for Exynos4415 clock controller Chanwoo Choi
2014-10-24 10:32 ` Sylwester Nawrocki
2014-10-24 10:34 ` Chanwoo Choi [this message]
2014-10-20 3:32 ` [PATCH 4/5] pinctrl: exynos: Add support for Exynos4415 Chanwoo Choi
2014-10-20 3:32 ` [PATCH 5/5] ARM: dts: Add dts files for Exynos4415 SoC Chanwoo Choi
2014-10-24 13:23 ` Daniel Drake
2014-10-24 13:30 ` Tomasz Figa
2014-10-24 13:34 ` Marek Szyprowski
2014-10-24 13:44 ` Daniel Drake
2014-10-24 13:53 ` Chanwoo Choi
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=544A2B4E.8090604@samsung.com \
--to=cw00.choi@samsung.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).