summaryrefslogtreecommitdiffstats
path: root/drivers/gpio
diff options
context:
space:
mode:
authorAlexandre Courbot <acourbot@nvidia.com>2014-10-29 17:13:14 +0900
committerLinus Walleij <linus.walleij@linaro.org>2014-10-30 16:41:47 +0100
commit2071d0968e564b4b4a11d36dc58de6e57188edd4 (patch)
treeba3b74d202a655a9a68fafb8ca1cffcc66101bbe /drivers/gpio
parentbd1dbc3b9d20f9fe43d7b06848fc821bc88124c3 (diff)
downloadop-kernel-dev-2071d0968e564b4b4a11d36dc58de6e57188edd4.zip
op-kernel-dev-2071d0968e564b4b4a11d36dc58de6e57188edd4.tar.gz
Documentation: gpio: guidelines for bindings
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 bindings: - All new bindings must have a meaningful name (e.g. the "gpios" property must not be used) - The only suffix allowed is "-gpios", no matter the number of descriptors in the property - GPIOs can only be grouped under the same property when they serve the same purpose, a case that should remain exceptional (e.g. bit-banged data lines). Signed-off-by: Alexandre Courbot <acourbot@nvidia.com> Cc: Rafael J. Wysocki <rjw@rjwysocki.net> Acked-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud