linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 6/6] leds: netdev trigger: allow setting initial values in device tree
Date: Mon, 18 Mar 2019 12:54:52 +0100	[thread overview]
Message-ID: <20190318115452.GE6101@amd> (raw)
In-Reply-To: <20190314140619.3309-7-linux@rasmusvillemoes.dk>

[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]

On Thu 2019-03-14 15:06:19, Rasmus Villemoes wrote:
> It can be quite convenient to initialize a netdev-triggered LED with a
> device name and setting the rx,tx,link properties from device tree,
> instead of having to do that in an init script (or udev rule) in
> userspace.
> 
> My main motivation for this is to be able to switch away from the
> deprecated CONFIG_CAN_LEDS. The example added to common.txt
> corresponds to switching linux,default-trigger = "can0-rxtx" to
> "netdev" and adding the indicated netdev subnode.
> 
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> ---
>  .../devicetree/bindings/leds/common.txt       | 11 +++++++
>  drivers/leds/trigger/ledtrig-netdev.c         | 30 +++++++++++++++++++
>  2 files changed, 41 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
> index 7cb88460a47c..f8078c4cf6f8 100644
> --- a/Documentation/devicetree/bindings/leds/common.txt
> +++ b/Documentation/devicetree/bindings/leds/common.txt
> @@ -43,6 +43,17 @@ Optional properties for child nodes:
>                  Documentation/ABI/testing/sysfs-class-led-trigger-netdev)
>                  to reflect the state and activity of a net device.
>  
> +                The optional child node netdev can be used to
> +                configure initial values for the link, rx, tx and
> +                device_name properties. For example,
> +
> +                netdev {
> +                    rx;
> +                    tx;
> +                    link;
> +                    device-name = "can0";

Well, NAK, as explained before. Use phandle.

Alternatively, adding comment why CONFIG_CAN_LEDS can not be removed
just yet near the deprecation note would be acceptable.

									Pavel
									
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2019-03-18 11:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190311144227.GA4404@amd>
     [not found] ` <20190313202615.22883-1-linux@rasmusvillemoes.dk>
2019-03-13 20:26   ` [PATCH 1/4] leds: netdev trigger: use memcpy in device_name_store Rasmus Villemoes
2019-03-14  9:29     ` Uwe Kleine-König
2019-03-14  9:57       ` Rasmus Villemoes
2019-03-14 10:04         ` Uwe Kleine-König
2019-03-14 10:14     ` Pavel Machek
2019-03-14 10:54       ` Rasmus Villemoes
2019-03-14 12:16         ` Pavel Machek
2019-03-13 20:26   ` [PATCH 2/4] leds: netdev trigger: factor out middle part of device_name_store Rasmus Villemoes
2019-03-14  9:31     ` Uwe Kleine-König
2019-03-14  9:57       ` Rasmus Villemoes
2019-03-14 10:15       ` Pavel Machek
2019-03-14 10:20         ` Uwe Kleine-König
2019-03-13 20:26   ` [PATCH 3/4] leds: netdev trigger: add documentation to leds/common.txt Rasmus Villemoes
2019-03-13 20:26   ` [PATCH 4/4] leds: netdev trigger: allow setting initial values in device tree Rasmus Villemoes
2019-03-14  9:36     ` Uwe Kleine-König
2019-03-14 10:28       ` Rasmus Villemoes
2019-03-14 10:29     ` Pavel Machek
2019-03-14 11:26       ` Rasmus Villemoes
2019-03-14 12:00         ` Pavel Machek
2019-03-14 13:19           ` Rasmus Villemoes
2019-03-17 19:11             ` Pavel Machek
2019-03-24 20:39               ` Rasmus Villemoes
2019-03-14 10:32     ` Jacek Anaszewski
     [not found]   ` <20190314140619.3309-1-linux@rasmusvillemoes.dk>
2019-03-14 14:06     ` [PATCH v2 1/6] leds: netdev trigger: use memcpy in device_name_store Rasmus Villemoes
2019-03-18 11:20       ` Pavel Machek
2019-03-26 19:53       ` Jacek Anaszewski
2019-03-27 15:26         ` Rasmus Villemoes
2019-03-27 21:20           ` Jacek Anaszewski
2019-03-27 21:31             ` Rasmus Villemoes
2019-03-27 21:45               ` Jacek Anaszewski
2019-03-14 14:06     ` [PATCH v2 2/6] leds: netdev trigger: factor out middle part of device_name_store Rasmus Villemoes
2019-03-18 11:24       ` Pavel Machek
2019-03-14 14:06     ` [PATCH v2 3/6] leds: netdev trigger: move newline handling back to device_name_store Rasmus Villemoes
2019-03-18 11:25       ` Pavel Machek
2019-03-14 14:06     ` [PATCH v2 4/6] leds: netdev trigger: move name length checking to netdev_trig_set_device Rasmus Villemoes
2019-03-18 11:26       ` Pavel Machek
2019-03-14 14:06     ` [PATCH v2 5/6] leds: netdev trigger: add documentation to leds/common.txt Rasmus Villemoes
2019-03-14 14:06     ` [PATCH v2 6/6] leds: netdev trigger: allow setting initial values in device tree Rasmus Villemoes
2019-03-14 14:24       ` Jacek Anaszewski
2019-03-14 15:05         ` Rasmus Villemoes
2019-03-14 15:36           ` Jacek Anaszewski
2019-03-18 11:54       ` Pavel Machek [this message]
2019-03-28 16:28       ` Rob Herring

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=20190318115452.GE6101@amd \
    --to=pavel@ucw.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=u.kleine-koenig@pengutronix.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).