On Fri, Oct 07, 2016 at 06:17:23PM +0300, Pantelis Antoniou wrote: > From: Georgi Vlaev <gvlaev@xxxxxxxxxxx> > > Add DT bindings document for the PTXPMB CPLD MFD device. > > Signed-off-by: Georgi Vlaev <gvlaev@xxxxxxxxxxx> > [Ported from Juniper kernel] > Signed-off-by: Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx> > --- > .../devicetree/bindings/mfd/jnx-ptxpmb-cpld.txt | 76 ++++++++++++++++++++++ > 1 file changed, 76 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/jnx-ptxpmb-cpld.txt > > diff --git a/Documentation/devicetree/bindings/mfd/jnx-ptxpmb-cpld.txt b/Documentation/devicetree/bindings/mfd/jnx-ptxpmb-cpld.txt > new file mode 100644 > index 0000000..cc3cbb9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/jnx-ptxpmb-cpld.txt > @@ -0,0 +1,76 @@ > +* Device tree bindings for Juniper's PTXPMB CPLD FPGA MFD driver > + > +The device supports a number I2C muxes, hardware watchdog and a gpio block. > +Those devices bindings are described in the jnx-i2c-mux-ptxpmb-cpld, > +jnx-ptxpmb-wdt and jnx-gpio-ptxpmb-cpld documents. > + > +Required properties: > + > +- compatible: "jnx,ptxpmb-cpld", "jnx,ngpmb-bcpld". They differ bcpld? looks like a typo? > + in the i2c-mux blocks. > + > +- reg: contains offset/length value for device state control > + registers space. > + > +Optional properties: > + > +- interrupts: The interrupt line(s) the /IRQ signal(s) for the device is > + connected to. > + > +- interrupt-parent: The parent interrupt controller. > + > +Example: > + > +cpld@0,0 { What bus is this on? If just simple-bus, then just '...@0' > + compatible = "jnx,ptxpmb-cpld"; > + reg = <0x0 0 0x10000>; -- 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