Message ID | 1422318639-20995-1-git-send-email-festevam@gmail.com |
---|---|
State | New |
Headers | show |
On Tue, Jan 27, 2015 at 9:30 AM, Fabio Estevam <festevam@gmail.com> wrote: > From: Fabio Estevam <fabio.estevam@freescale.com> > > As explained in this file: > > "GPIOs mappings are defined in the consumer device's node, in a property named > <function>-gpios" > > So fix the example to match the convention. Acked-by: Alexandre Courbot <acourbot@nvidia.com> -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 26 Jan 2015 22:30:39 -0200 Fabio Estevam <festevam@gmail.com> wrote: > As explained in this file: > > "GPIOs mappings are defined in the consumer device's node, in a property named > <function>-gpios" > > So fix the example to match the convention. OK, I've applied this to the docs tree, thanks. jon -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/gpio/board.txt b/Documentation/gpio/board.txt index 4452786..8b35f51 100644 --- a/Documentation/gpio/board.txt +++ b/Documentation/gpio/board.txt @@ -31,7 +31,7 @@ through gpiod_get(). For example: <&gpio 16 GPIO_ACTIVE_HIGH>, /* green */ <&gpio 17 GPIO_ACTIVE_HIGH>; /* blue */ - power-gpio = <&gpio 1 GPIO_ACTIVE_LOW>; + power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; }; This property will make GPIOs 15, 16 and 17 available to the driver under the