Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
To: Bintian Wang <bintian.wang@huawei.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        catalin.marinas@arm.com, will.deacon@arm.com,
        devicetree@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
        mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
        galak@codeaurora.org, khilman@linaro.org, rob.herring@linaro.org,
        zhangfei.gao@linaro.org, haojian.zhuang@linaro.org,
        xuwei5@hisilicon.com, jh80.chung@samsung.com, olof@lixom.net,
        yanhaifeng@gmail.com, sboyd@codeaurora.org, xuejiancheng@huawei.com,
        sledge.yanwei@huawei.com, tomeu.vizoso@collabora.com,
        linux@arm.linux.org.uk, guodong.xu@linaro.org,
        jorge.ramirez-ortiz@linaro.org, tyler.baker@linaro.org,
        khilman@kernel.org, pebolle@tiscali.nl, arnd@arndb.de,
        marc.zyngier@arm.com
From: Michael Turquette <mturquette@linaro.org>
In-Reply-To: <1432865319-20413-3-git-send-email-bintian.wang@huawei.com>
Cc: xuyiping@hisilicon.com, wangbinghui@hisilicon.com,
        zhenwei.wang@hisilicon.com, victor.lixin@hisilicon.com,
        puck.chen@hisilicon.com, dan.zhao@hisilicon.com, huxinwei@huawei.com,
        bintian.wang@huawei.com, z.liuxinliang@huawei.com, heyunlei@huawei.com,
        kong.kongxinwei@hisilicon.com, wangbintian@gmail.com, w.f@huawei.com,
        liguozhu@hisilicon.com
References: <1432865319-20413-1-git-send-email-bintian.wang@huawei.com>
 <1432865319-20413-3-git-send-email-bintian.wang@huawei.com>
Message-ID: <20150603163139.6017.73279@quantum>
User-Agent: alot/0.3.5
Subject: Re: [PATCH v8 2/7] clk: hi6220: Document devicetree bindings for hi6220 clock
Date: Wed, 03 Jun 2015 09:31:39 -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2287
Lines: 63

Quoting Bintian Wang (2015-05-28 19:08:34)
> Document DT files bindings for Hisilicon hi6220 clock.
> 
> Signed-off-by: Bintian Wang <bintian.wang@huawei.com>
> Acked-by: Haojian Zhuang <haojian.zhuang@linaro.org>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Acked-by: Stephen Boyd <sboyd@codeaurora.org>

Acked-by: Michael Turquette <mturquette@linaro.org>

> ---
>  .../devicetree/bindings/clock/hi6220-clock.txt     | 34 ++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/clock/hi6220-clock.txt
> 
> diff --git a/Documentation/devicetree/bindings/clock/hi6220-clock.txt b/Documentation/devicetree/bindings/clock/hi6220-clock.txt
> new file mode 100644
> index 0000000..53ddb19
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/hi6220-clock.txt
> @@ -0,0 +1,34 @@
> +* Hisilicon Hi6220 Clock Controller
> +
> +Clock control registers reside in different Hi6220 system controllers,
> +please refer the following document to know more about the binding rules
> +for these system controllers:
> +
> +Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt
> +
> +Required Properties:
> +
> +- compatible: the compatible should be one of the following strings to
> +       indicate the clock controller functionality.
> +
> +       - "hisilicon,hi6220-aoctrl"
> +       - "hisilicon,hi6220-sysctrl"
> +       - "hisilicon,hi6220-mediactrl"
> +       - "hisilicon,hi6220-pmctrl"
> +
> +- reg: physical base address of the controller and length of memory mapped
> +  region.
> +
> +- #clock-cells: should be 1.
> +
> +For example:
> +       sys_ctrl: sys_ctrl {
> +               compatible = "hisilicon,hi6220-sysctrl", "syscon";
> +               reg = <0x0 0xf7030000 0x0 0x2000>;
> +               #clock-cells = <1>;
> +       };
> +
> +Each clock is assigned an identifier and client nodes use this identifier
> +to specify the clock which they consume.
> +
> +All these identifier could be found in <dt-bindings/clock/hi6220-clock.h>.
> -- 
> 1.9.1
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/