On Thu, Jun 06, 2013 at 09:06:51AM +0800, tang yuantian wrote: > From: Tang Yuantian <yuantian.tang@xxxxxxxxxxxxx> > > The following SoCs will be affected: p2041, p3041, p4080, > p5020, p5040, b4420, b4860, t4240 > > Signed-off-by: Tang Yuantian <Yuantian.Tang@xxxxxxxxxxxxx> > Signed-off-by: Li Yang <leoli@xxxxxxxxxxxxx> > > --- > v3: > - fix typo > v2: > - add t4240, b4420, b4860 support > - remove pll/4 clock from p2041, p3041 and p5020 board > > arch/powerpc/boot/dts/fsl/b4420si-post.dtsi | 32 ++++++++- > arch/powerpc/boot/dts/fsl/b4420si-pre.dtsi | 2 + > arch/powerpc/boot/dts/fsl/b4860si-post.dtsi | 32 ++++++++- > arch/powerpc/boot/dts/fsl/b4860si-pre.dtsi | 4 ++ > arch/powerpc/boot/dts/fsl/p2041si-post.dtsi | 54 ++++++++++++++- > arch/powerpc/boot/dts/fsl/p2041si-pre.dtsi | 4 ++ > arch/powerpc/boot/dts/fsl/p3041si-post.dtsi | 54 ++++++++++++++- > arch/powerpc/boot/dts/fsl/p3041si-pre.dtsi | 4 ++ > arch/powerpc/boot/dts/fsl/p4080si-post.dtsi | 100 +++++++++++++++++++++++++++- > arch/powerpc/boot/dts/fsl/p4080si-pre.dtsi | 8 +++ > arch/powerpc/boot/dts/fsl/p5020si-post.dtsi | 38 ++++++++++- > arch/powerpc/boot/dts/fsl/p5020si-pre.dtsi | 2 + > arch/powerpc/boot/dts/fsl/p5040si-post.dtsi | 54 ++++++++++++++- > arch/powerpc/boot/dts/fsl/p5040si-pre.dtsi | 4 ++ > arch/powerpc/boot/dts/fsl/t4240si-post.dtsi | 77 ++++++++++++++++++++- > arch/powerpc/boot/dts/fsl/t4240si-pre.dtsi | 12 ++++ > 16 files changed, 473 insertions(+), 8 deletions(-) > > diff --git a/arch/powerpc/boot/dts/fsl/b4420si-post.dtsi b/arch/powerpc/boot/dts/fsl/b4420si-post.dtsi > index 5a6615d..b69d6e5 100644 > --- a/arch/powerpc/boot/dts/fsl/b4420si-post.dtsi > +++ b/arch/powerpc/boot/dts/fsl/b4420si-post.dtsi > @@ -85,7 +85,37 @@ > }; > > clockgen: global-utilities@e1000 { > - compatible = "fsl,b4420-clockgen", "fsl,qoriq-clockgen-2.0"; > + compatible = "fsl,b4420-clockgen", "fsl,qoriq-clockgen-2.0", > + "fixed-clock"; > + clock-output-names = "sysclk"; > + #clock-cells = <0>; Does U-Boot fill in clock-frequency here? > + #address-cells = <1>; > + #size-cells = <0>; > + pll0: pll0@800 { > + #clock-cells = <1>; > + reg = <0x800>; > + compatible = "fsl,core-pll-clock"; > + clocks = <&clockgen>; > + clock-output-names = "pll0", "pll0-div2", "pll0-div4"; > + }; > + pll1: pll1@820 { > + #clock-cells = <1>; > + reg = <0x820>; > + compatible = "fsl,core-pll-clock"; > + clocks = <&clockgen>; > + clock-output-names = "pll1", "pll1-div2", "pll1-div4"; > + }; Please leave a blank line between properties and nodes, and between nodes. What does reg represent? Where is the binding for this? The compatible is too vague. > + mux0: mux0@0 { > + #clock-cells = <0>; > + reg = <0x0>; > + compatible = "fsl,core-mux-clock"; > + clocks = <&pll0 0>, <&pll0 1>, <&pll0 2>, > + <&pll1 0>, <&pll1 1>, <&pll1 2>; > + clock-names = "pll0_0", "pll0_1", "pll0_2", > + "pll1_0", "pll1_1", "pll1_2"; > + clock-output-names = "cmux0"; > + }; What does reg represent? Where is the binding for this? The compatible is too vague. -Scott -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html