Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752677AbbLNB5Q (ORCPT ); Sun, 13 Dec 2015 20:57:16 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:62782 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751697AbbLNB5O (ORCPT ); Sun, 13 Dec 2015 20:57:14 -0500 Subject: Re: [PATCH v3 2/7] clk: hisilicon: add dt-binding document for Hi3519 CRG To: Rob Herring References: <1449819921-18464-1-git-send-email-xuejiancheng@huawei.com> <1449819921-18464-3-git-send-email-xuejiancheng@huawei.com> <20151211151909.GA21272@rob-hp-laptop> CC: , , , , , , , , , , , , , , , , , , , , , , , , From: xuejiancheng Message-ID: <566E1F56.3070800@huawei.com> Date: Mon, 14 Dec 2015 09:45:58 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151211151909.GA21272@rob-hp-laptop> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.217.211] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.566E1F69.0108,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 41b2eb707d3c5d739dd2531780320e74 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2928 Lines: 102 On 2015/12/11 23:19, Rob Herring wrote: > On Fri, Dec 11, 2015 at 03:45:16PM +0800, Jiancheng Xue wrote: >> add dt-binding document for Hi3519 CRG block >> >> Signed-off-by: Jiancheng Xue >> --- >> .../devicetree/bindings/clock/hi3519-crg.txt | 46 ++++++++++++++++++++++ >> 1 file changed, 46 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/clock/hi3519-crg.txt >> >> diff --git a/Documentation/devicetree/bindings/clock/hi3519-crg.txt b/Documentation/devicetree/bindings/clock/hi3519-crg.txt >> new file mode 100644 >> index 0000000..e0d30a4 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/clock/hi3519-crg.txt >> @@ -0,0 +1,46 @@ >> +* Hisilicon Hi3519 Clock and Reset Generator(CRG) >> + >> +The Hi3519 CRG module provides clock and reset signals to various >> +controllers within the SoC. >> + >> +This binding uses the following bindings: >> + Documentation/devicetree/bindings/clock/clock-bindings.txt >> + Documentation/devicetree/bindings/reset/reset.txt >> + >> +Required Properties: >> + >> +- compatible: should be one of the following. >> + - "hisilicon,hi3519-crg" - controller compatible with Hi3519 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 use this identifier >> +to specify the clock which they consume. >> + >> +All these identifier could be found in . > > This header should be part of this patch. Because the header is also depended on by the clock driver. It's also a problem if I separate it from the clock driver patch. Is it OK if I put this binding file into the clock driver patch? > >> + >> +- #reset-cells: should be 2. >> + >> +A reset signal can be controlled by writing a bit register in the CRG module. >> +The reset specifier consists of two cells. The first cell represents the >> +register offset relative to the base address. The second cell represents the >> +bit index in the register. >> + >> +Example: CRG nodes >> +CRG: clock-reset-controller { > > clock-reset-controller@12010000 OK. > >> + compatible = "hisilicon,hi3519-crg"; >> + reg = <0x12010000 0x10000>; >> + #clock-cells = <1>; >> + #reset-cells = <2>; >> +}; >> + >> +Example: consumer nodes >> +i2c0: i2c@0x12110000 { > > Drop '0x' OK. > >> + compatible = "hisilicon,hi3519-i2c"; >> + reg = <0x12110000 0x1000>; >> + clocks = <&CRG HI3519_I2C0_RST>;*/ >> + resets = <&CRG 0xE4 0>; > > lowercase hex please OK. > >> +}; >> -- >> 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/