On Tue, Apr 10, 2018 at 09:30:03AM +0100, Michel Pollet wrote: > The Renesas RZ/N1 Family (Part #R9A06G0xx) has a multi-function > system controller. This documents the node used to encapsulate > it's sub drivers. > > Signed-off-by: Michel Pollet <michel.pol...@bp.renesas.com> > --- > .../bindings/mfd/renesas,rzn1-sysctrl.txt | 23 > ++++++++++++++++++++++ > 1 file changed, 23 insertions(+) > create mode 100644 > Documentation/devicetree/bindings/mfd/renesas,rzn1-sysctrl.txt > > diff --git a/Documentation/devicetree/bindings/mfd/renesas,rzn1-sysctrl.txt > b/Documentation/devicetree/bindings/mfd/renesas,rzn1-sysctrl.txt > new file mode 100644 > index 0000000..9897f8f > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/renesas,rzn1-sysctrl.txt > @@ -0,0 +1,23 @@ > +DT bindings for the Renesas RZ/N1 System Controller > + > +== System Controller Node == > + > +The system controller node currently only hosts a single sub-node to handle > +the rebooting of the CPU. Eventually it will host the clock driver, SMP > +start handler, watchdog etc.
Please submit a complete binding for the h/w block. Again, if the only reason you have sub nodes is to define compatible strings and in turn enumerate drivers, then you don't need the nodes in DT. DT is not the only way to instantiate drivers. Rob