mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Richard Purdie" <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] DT: leds: Improve examples by adding some context
Date: Tue, 06 Dec 2016 12:34:55 +0100	[thread overview]
Message-ID: <5eee6421-1e6c-3955-652c-dedd275b5827@samsung.com> (raw)
In-Reply-To: <20161206083203.1726-1-zajec5@gmail.com>

Hi Rafał,

Thanks for the patch.

On 12/06/2016 09:32 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> During my work on some new LED trigger I tried adding example similar to
> the existing ones which received following comment from Rob:
>> It's not really clear in the example this is an LED node as it is
>> incomplete.
>
> Keeping that in mind I suggest adding context for the existing example
> entries in hope to make documentation more clear.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> Should this patch go through linux-leds tree?
>
> Richard, Jacek: would you take it?
> ---
>  Documentation/devicetree/bindings/leds/common.txt | 28 +++++++++++++++--------
>  1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
> index 696be57..24b6560 100644
> --- a/Documentation/devicetree/bindings/leds/common.txt
> +++ b/Documentation/devicetree/bindings/leds/common.txt
> @@ -61,16 +61,24 @@ property can be omitted.
>
>  Examples:
>
> -system-status {
> -	label = "Status";
> -	linux,default-trigger = "heartbeat";
> -	...
> +gpio-leds {
> +	compatible = "gpio-leds";
> +
> +	system-status {
> +		label = "Status";
> +		linux,default-trigger = "heartbeat";
> +		gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>;
> +	};
>  };
>
> -camera-flash {
> -	label = "Flash";
> -	led-sources = <0>, <1>;
> -	led-max-microamp = <50000>;
> -	flash-max-microamp = <320000>;
> -	flash-max-timeout-us = <500000>;
> +max77693-led {
> +	compatible = "maxim,max77693-led";
> +
> +	camera-flash {
> +		label = "Flash";
> +		led-sources = <0>, <1>;
> +		led-max-microamp = <50000>;
> +		flash-max-microamp = <320000>;
> +		flash-max-timeout-us = <500000>;
> +	};
>  };
>

Although this file documents a sub-node properties it will be indeed
useful to have the parent node in the example as well.

Applied to the for-4.11 branch of linux-leds.git.

-- 
Best regards,
Jacek Anaszewski

      reply	other threads:[~2016-12-06 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161206083302epcas1p170eb3f7dd0ca9b86d580563605182225@epcas1p1.samsung.com>
2016-12-06  8:32 ` Rafał Miłecki
2016-12-06 11:34   ` Jacek Anaszewski [this message]

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=5eee6421-1e6c-3955-652c-dedd275b5827@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=zajec5@gmail.com \
    /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

all inboxes | Powered by JetHome®