Hi Geert, Thank you for the patch.
On Thursday 27 March 2014 21:47:37 Geert Uytterhoeven wrote: > From: Geert Uytterhoeven <[email protected]> > > Signed-off-by: Geert Uytterhoeven <[email protected]> > Cc: Linus Walleij <[email protected]> > Cc: Laurent Pinchart <[email protected]> > Cc: [email protected] > Cc: [email protected] > --- > .../devicetree/bindings/gpio/renesas,gpio-rcar.txt | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt index > f61cef74a212..9ccbe50dcec2 100644 > --- a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > +++ b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > @@ -21,6 +21,10 @@ Required Properties: > GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW flags are supported. > - gpio-ranges: Range of pins managed by the GPIO controller. > > +Optional properties: > + > + - clocks: Must contain a reference to the functional clock. > + I would make the property mandatory. Obviously the driver needs to consider it as optional in order not to break the DT ABI, but the specification should make it mandatory in order to ensure that all future implementations will specify the clock. > Please refer to gpio.txt in this directory for details of gpio-ranges > property and the common GPIO bindings used by client devices. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
