On Tue, Oct 11, 2016 at 11:00 AM, Paul Burton <paul.burton@xxxxxxxxxx> wrote: > On Monday, 10 October 2016 08:01:21 BST Rob Herring wrote: >> On Wed, Oct 05, 2016 at 06:18:22PM +0100, Paul Burton wrote: >> > Add device tree binding documentation for the clocks provided by the >> > MIPS Boston development board from Imagination Technologies, and a >> > header file describing the available clocks for use by device trees & >> > driver. >> > >> > Signed-off-by: Paul Burton <paul.burton@xxxxxxxxxx> >> > Cc: Michael Turquette <mturquette@xxxxxxxxxxxx> >> > Cc: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> >> > Cc: linux-clk@xxxxxxxxxxxxxxx >> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> >> > Cc: Mark Rutland <mark.rutland@xxxxxxx> >> > Cc: devicetree@xxxxxxxxxxxxxxx >> > >> > --- >> > >> > Changes in v3: None >> > Changes in v2: >> > - Add BOSTON_CLK_INPUT to expose the input clock. >> > >> > .../devicetree/bindings/clock/img,boston-clock.txt | 27 >> > ++++++++++++++++++++++ include/dt-bindings/clock/boston-clock.h >> > | 14 +++++++++++ 2 files changed, 41 insertions(+) >> > create mode 100644 >> > Documentation/devicetree/bindings/clock/img,boston-clock.txt create mode >> > 100644 include/dt-bindings/clock/boston-clock.h >> > >> > diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt >> > b/Documentation/devicetree/bindings/clock/img,boston-clock.txt new file >> > mode 100644 >> > index 0000000..c01ea60 >> > --- /dev/null >> > +++ b/Documentation/devicetree/bindings/clock/img,boston-clock.txt >> > @@ -0,0 +1,27 @@ >> > +Binding for Imagination Technologies MIPS Boston clock sources. >> > + >> > +This binding uses the common clock binding[1]. >> > + >> > +[1] Documentation/devicetree/bindings/clock/clock-bindings.txt >> > + >> > +Required properties: >> > +- compatible : Should be "img,boston-clock". >> > +- #clock-cells : Should be set to 1. >> > + Values available for clock consumers can be found in the header file: >> > + <dt-bindings/clock/boston-clock.h> >> > +- regmap : Phandle to the Boston platform register system controller. >> > + This should contain a phandle to the system controller node covering >> > the >> > + platform registers provided by the Boston board. >> >> Can you just make the clock node a child of the system controller and >> drop this? >> >> Rob > > Hi Rob, > > (Apologies to anyone who received my last; my mail client seems to be > misconfigured & previously sent HTML mail.) > > As I mentioned before technically that could be done, but it would really not > be at all reflective of the hardware & so seems somewhat contrary to the > purpose of a device tree. Given that you need a reference back to the system controller, it does match the h/w. The system controller h/w contains various functions, therefore the system controller node should contain nodes for those functions (or the sys ctrlr itself could be the clock provider node with no child nodes). Otherwise, what is the parent of the clock node? Root? Root should generally be the top level devices of the SoC, though it gets used for things which have no good parent. Rob
