Hi Geert, Thank you for the patch.
On Monday 14 April 2014 20:33:12 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] Acked-by: Laurent Pinchart <[email protected]> > --- > v2: > - Functional clock is mandatory depending on hardware (thanks, Laurent) > --- > .../devicetree/bindings/gpio/renesas,gpio-rcar.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt index > f61cef74a212..941a26aa4322 100644 > --- a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > +++ b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt > @@ -21,6 +21,12 @@ 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. The property > is + mandatory if the hardware implements a controllable functional > clock for + the GPIO instance. > + > 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 devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
