linux-kernel - Re: [PATCH v8 2/7] clk: hi6220: Document devicetree bindings for hi6220 clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 03 Jun 2015 09:31:39 -0700
From:	Michael Turquette <mturquette@...aro.org>
To:	Bintian Wang <bintian.wang@...wei.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	catalin.marinas@....com, will.deacon@....com,
	devicetree@...r.kernel.org, robh+dt@...nel.org, pawel.moll@....com,
	mark.rutland@....com, ijc+devicetree@...lion.org.uk,
	galak@...eaurora.org, khilman@...aro.org, rob.herring@...aro.org,
	zhangfei.gao@...aro.org, haojian.zhuang@...aro.org,
	xuwei5@...ilicon.com, jh80.chung@...sung.com, olof@...om.net,
	yanhaifeng@...il.com, sboyd@...eaurora.org,
	xuejiancheng@...wei.com, sledge.yanwei@...wei.com,
	tomeu.vizoso@...labora.com, linux@....linux.org.uk,
	guodong.xu@...aro.org, jorge.ramirez-ortiz@...aro.org,
	tyler.baker@...aro.org, khilman@...nel.org, pebolle@...cali.nl,
	arnd@...db.de, marc.zyngier@....com
Cc:	xuyiping@...ilicon.com, wangbinghui@...ilicon.com,
	zhenwei.wang@...ilicon.com, victor.lixin@...ilicon.com,
	puck.chen@...ilicon.com, dan.zhao@...ilicon.com,
	huxinwei@...wei.com, bintian.wang@...wei.com,
	z.liuxinliang@...wei.com, heyunlei@...wei.com,
	kong.kongxinwei@...ilicon.com, wangbintian@...il.com,
	w.f@...wei.com, liguozhu@...ilicon.com
Subject: Re: [PATCH v8 2/7] clk: hi6220: Document devicetree bindings for hi6220 clock

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

Acked-by: Michael Turquette <mturquette@...aro.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/