Re: [PATCH v2] Documentation: gpio: guidelines for bindings

2014-10-30 Thread Linus Walleij
On Wed, Oct 29, 2014 at 9:13 AM, Alexandre Courbot wrote: > Now that ACPI supports named GPIO properties, either through ACPI 5.1 or > the per-driver ACPI GPIO mappings, we can be more narrow about the way > GPIOs should be specified in Device Tree bindings. > > This patch updates the GPIO DT bin

Re: [PATCH v2] Documentation: gpio: guidelines for bindings

2014-10-29 Thread Mika Westerberg
On Wed, Oct 29, 2014 at 05:13:14PM +0900, Alexandre Courbot wrote: > Now that ACPI supports named GPIO properties, either through ACPI 5.1 or > the per-driver ACPI GPIO mappings, we can be more narrow about the way > GPIOs should be specified in Device Tree bindings. > > This patch updates the GPI

Re: [PATCH v2] Documentation: gpio: guidelines for bindings

2014-10-29 Thread Arnd Bergmann
On Wednesday 29 October 2014 17:13:14 Alexandre Courbot wrote: > Now that ACPI supports named GPIO properties, either through ACPI 5.1 or > the per-driver ACPI GPIO mappings, we can be more narrow about the way > GPIOs should be specified in Device Tree bindings. > > This patch updates the GPIO DT

[PATCH v2] Documentation: gpio: guidelines for bindings

2014-10-29 Thread Alexandre Courbot
Now that ACPI supports named GPIO properties, either through ACPI 5.1 or the per-driver ACPI GPIO mappings, we can be more narrow about the way GPIOs should be specified in Device Tree bindings. This patch updates the GPIO DT bindings documentation to highlight the following rules for new GPIO bin