[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56C6664F.8070600@rock-chips.com>
Date: Fri, 19 Feb 2016 08:48:15 +0800
From: Jianqun Xu <jay.xu@...k-chips.com>
To: Rob Herring <robh@...nel.org>
Cc: heiko@...ech.de, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
jwerner@...omium.org, broonie@...nel.org, catalin.marinas@....com,
will.deacon@....com, sboyd@...eaurora.org,
linus.walleij@...aro.org, sjoerd.simons@...labora.co.uk,
huangtao@...k-chips.com, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, Xing Zheng <zhengxing@...k-chips.com>
Subject: Re: [PATCH 5/6] dt-bindings: add documentation of rk3399 clock
controller
Hi Rob
在 18/02/2016 22:36, Rob Herring 写道:
> On Wed, Feb 17, 2016 at 09:54:49AM +0800, jianqun.xu wrote:
>> From: Xing Zheng <zhengxing@...k-chips.com>
>>
>> Add the devicetree binding for the cru on the rk3399 which quite
>> similar structured as previous clock controllers.
>>
>> Signed-off-by: Xing Zheng <zhengxing@...k-chips.com>
>> ---
>> .../bindings/clock/rockchip,rk3399-cru.txt | 82 ++++++++++++++++++++++
>> 1 file changed, 82 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt
>>
>> diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt
>> new file mode 100644
>> index 0000000..07bcc6e
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt
>> @@ -0,0 +1,82 @@
>> +* Rockchip RK3399 Clock and Reset Unit
>
> [...]
>
>> +Example: General Register Files
>> +
>> + pmugrf: syscon@...20000 {
>> + compatible = "rockchip,rk3399-pmugrf", "syscon";
>
> Is this documented?
Since there is no documentation for rockchip grf from early SoCs, I
think if we need to add a new devicetree documentation, such as
Documentation/devicetree/bindings/clock/rockchip,rk3399-grf.txt ?
If you agree, I will add it in next patch
>
>> + reg = <0x0 0xff320000 0x0 0x1000>;
>> + };
>> +
>> + grf: syscon@...70000 {
>> + compatible = "rockchip,rk3399-grf", "syscon";
>
> ditto.
>
>> + reg = <0x0 0xff770000 0x0 0x10000>;
>> + };
>> +
>> +Example: Clock controller node:
>> +
>> + pmucru: pmu-clock-controller@...50000 {
>> + compatible = "rockchip,rk3399-pmucru";
>> + reg = <0x0 0xff750000 0x0 0x1000>;
>> + #clock-cells = <1>;
>> + #reset-cells = <1>;
>> + };
>> +
>> + cru: clock-controller@...60000 {
>> + compatible = "rockchip,rk3399-cru";
>> + reg = <0x0 0xff760000 0x0 0x1000>;
>> + rockchip,grf = <&grf>;
>> + #clock-cells = <1>;
>> + #reset-cells = <1>;
>> + };
>> +
>> +Example: UART controller node that consumes the clock generated by the clock
>> + controller:
>> +
>> + uart0: serial@...a0000 {
>> + compatible = "rockchip,rk3399-uart", "snps,dw-apb-uart";
>> + reg = <0x0 0xff180000 0x0 0x100>;
>> + clocks = <&cru SCLK_UART0>, <&cru PCLK_UART0>;
>> + clock-names = "baudclk", "apb_pclk";
>> + interrupts = <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>;
>> + reg-shift = <2>;
>> + reg-io-width = <4>;
>> + };
>> --
>> 1.9.1
>>
>>
>
>
>
Powered by blists - more mailing lists