From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Olliver Schinagl <oliver+list@schinagl.nl>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Olliver Schinagl <oliver@schinagl.nl>,
Robin Gong <b38343@freescale.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Aaron Lu <aaron.lu@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Grant Likely <grant.likely@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
Alexander Shiyan <shc_work@mail.ru>,
Jingoo Han <jg1.han@samsung.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v1 3/4] leds: Let the binding document example for leds-gpio follow the gpio bindings
Date: Wed, 7 Jan 2015 15:56:15 -0800 [thread overview]
Message-ID: <20150107235615.GB6670@dtor-ws> (raw)
In-Reply-To: <1420621722-7428-4-git-send-email-oliver+list@schinagl.nl>
On Wed, Jan 07, 2015 at 10:08:41AM +0100, Olliver Schinagl wrote:
> From: Olliver Schinagl <oliver@schinagl.nl>
>
> In the gpio bindings documents it is requested to use the marco's in
> include/dt-bindings/gpio/gpio.h whenever possible. The gpios in the led
> drivers don't seem to form an exception, so update the example in the
> document bindings.
>
> Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
> ---
> Documentation/devicetree/bindings/leds/leds-gpio.txt | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-gpio.txt b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> index f77148f..d544cf1 100644
> --- a/Documentation/devicetree/bindings/leds/leds-gpio.txt
> +++ b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> @@ -26,16 +26,18 @@ LED sub-node properties:
>
> Examples:
>
> +#include <dt-bindings/gpio/gpio.h>
> +
> leds {
> compatible = "gpio-leds";
> hdd {
> label = "IDE Activity";
> - gpios = <&mcu_pio 0 1>; /* Active low */
> + gpios = <&mcu_pio 0 GPIO_ACTIVE_LOW>;
> linux,default-trigger = "ide-disk";
> };
>
> fault {
> - gpios = <&mcu_pio 1 0>;
> + gpios = <&mcu_pio 1 GPIO_ACTIVE_HIGH>;
> /* Keep LED on if BIOS detected hardware fault */
> default-state = "keep";
> };
> @@ -44,11 +46,11 @@ leds {
> run-control {
> compatible = "gpio-leds";
> red {
> - gpios = <&mpc8572 6 0>;
> + gpios = <&mpc8572 6 GPIO_ACTIVE_HIHG>;
Typo, s/HIHG/HIGH/
> default-state = "off";
> };
> green {
> - gpios = <&mpc8572 7 0>;
> + gpios = <&mpc8572 7 GPIO_ACTIVE_HIGH>;
> default-state = "on";
> };
> };
> @@ -57,7 +59,7 @@ leds {
> compatible = "gpio-leds";
>
> charger-led {
> - gpios = <&gpio1 2 0>;
> + gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
> linux,default-trigger = "max8903-charger-charging";
> retain-state-suspended;
> };
> --
> 2.1.4
>
--
Dmitry
next prev parent reply other threads:[~2015-01-07 23:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 9:08 [PATCH v1 0/4] Let leds use named gpios Olliver Schinagl
2015-01-07 9:08 ` [PATCH v1 1/4] gpio:gpiolib: use static const char const * for a suffixes array Olliver Schinagl
2015-01-14 12:35 ` Linus Walleij
2015-01-07 9:08 ` [PATCH v1 2/4] gpio: add parameter to allow the use named gpios Olliver Schinagl
2015-01-08 0:15 ` Dmitry Torokhov
2015-01-14 12:36 ` Linus Walleij
2015-01-19 4:04 ` Alexandre Courbot
2015-01-21 21:44 ` Olliver Schinagl
2015-01-23 9:16 ` Alexandre Courbot
2015-01-07 9:08 ` [PATCH v1 3/4] leds: Let the binding document example for leds-gpio follow the gpio bindings Olliver Schinagl
2015-01-07 23:56 ` Dmitry Torokhov [this message]
2015-01-08 1:45 ` Rob Herring
2015-01-14 12:38 ` Linus Walleij
[not found] ` <1420621722-7428-1-git-send-email-oliver+list-dxLnbx3+1qmEVqv0pETR8A@public.gmane.org>
2015-01-07 9:08 ` [PATCH v1 4/4] leds: no longer use unnamed gpios Olliver Schinagl
[not found] ` <1420621722-7428-5-git-send-email-oliver+list-dxLnbx3+1qmEVqv0pETR8A@public.gmane.org>
2015-01-07 23:55 ` Dmitry Torokhov
2015-01-08 8:45 ` Olliver Schinagl
2015-01-08 14:40 ` Rob Herring
2015-01-08 22:12 ` Dmitry Torokhov
2015-01-14 12:45 ` Linus Walleij
2015-01-14 13:20 ` Olliver Schinagl
2015-01-19 3:43 ` Alexandre Courbot
2015-01-19 4:09 ` Alexandre Courbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150107235615.GB6670@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aaron.lu@intel.com \
--cc=b38343@freescale.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jg1.han@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oliver+list@schinagl.nl \
--cc=oliver@schinagl.nl \
--cc=pawel.moll@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=shc_work@mail.ru \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).