On 18/11/15 16:03, Ray Jui wrote: > > > On 11/18/2015 3:13 PM, Jon Mason wrote: >> Add device tree entries for clock support for Broadcom Northstar 2 SoC >> >> Signed-off-by: Jon Mason <jonmason@xxxxxxxxxxxx> >> --- >> arch/arm64/boot/dts/broadcom/ns2.dtsi | 80 >> ++++++++++++++++++++++++++++++++++- >> 1 file changed, 79 insertions(+), 1 deletion(-) >> >> diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi >> b/arch/arm64/boot/dts/broadcom/ns2.dtsi >> index 9610822..a510d3a 100644 >> --- a/arch/arm64/boot/dts/broadcom/ns2.dtsi >> +++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi >> @@ -31,6 +31,7 @@ >> */ >> >> #include <dt-bindings/interrupt-controller/arm-gic.h> >> +#include <dt-bindings/clock/bcm-ns2.h> >> >> /memreserve/ 0x84b00000 0x00000008; >> >> @@ -109,6 +110,33 @@ >> <&A57_3>; >> }; >> >> + clocks { > > Is this a new convention? That is, group all clocks without a base > register address in a node named "clocks", but at the same time, put all > other clocks with base register address under a bus node. I do not think that is new, lots of platforms do that. The clock providers/controllers would typically be in the 'bus' nodes because it has a register interface, while the synthetic clocks would be under 'clocks'. -- Florian -- 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