From patchwork Wed Mar 13 20:26:15 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Rasmus Villemoes X-Patchwork-Id: 1056205 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=rasmusvillemoes.dk Authentication-Results: ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=rasmusvillemoes.dk header.i=@rasmusvillemoes.dk header.b="KaX15mB5"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 44KNfb685Kz9s6w for ; Thu, 14 Mar 2019 07:26:47 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727173AbfCMU0p (ORCPT ); Wed, 13 Mar 2019 16:26:45 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:40054 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727318AbfCMU0Z (ORCPT ); Wed, 13 Mar 2019 16:26:25 -0400 Received: by mail-ed1-f68.google.com with SMTP id r23so2696014edm.7 for ; Wed, 13 Mar 2019 13:26:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rasmusvillemoes.dk; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=391achGSbEwlOcz+XVWozH1Rc+0QP7rUHnU2cfCzNwc=; b=KaX15mB5igIUUWZAPZiEgalxtbUj0wwluQRyzctZsOEbWsvMLuMNrKMDqHmSUkCcIC EjxYEa9/hMcYWsYOZ0vT8RdDrtNYks7wU7AZikdqVfMf0hrd8+OAJWZiQVgg95D5zrif FFrpNfNy1dOSIcOpm6ykf+iTdYa1wSYSDDNDI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=391achGSbEwlOcz+XVWozH1Rc+0QP7rUHnU2cfCzNwc=; b=BzlivT2jiRaxdbgdjQYueIMwCyyPuVwUfBgn/k9DNcyoqIPf0nDh7EzGK3islOqOy8 2rgppD4ym1bgH+rbIGGLvgMonnzveF6pKdWn0+HaumYaIKDwLTImbHOuyVPdVFcihHm2 FGU2e8xYJ8ICjXNxXrSpQUqqRQHtbtolPAibGnynSThkeayt7e+gs6wXJjby1lGYzzKp /h6XmtQQGaSazmHcwftBCdVfMbZ8MH2divzHs/QAtWQtKj6Ik8GUKVGSsL3e3osILg7z bXi/6W7YgpeRNx9M2E58Rp+3dqX5gNDGZOfPOip+LlxoVL8i4EgeTEiwupH5hVfYIOvd ELeA== X-Gm-Message-State: APjAAAWoRHWD+tXyirHgvBb9PPPlKLxFDEyON2JeGFtwEUbIZYqWNhYA ZdXHRJf5NBCwR2P8aRXoBnlBcQ== X-Google-Smtp-Source: APXvYqxo34nX/yvPeKfKsjxlXoLQsPsg6Z49sS7OtuM8hFIOIE2Jx6+qAVJ254lkSYlnNBjPP4xrGw== X-Received: by 2002:a50:b613:: with SMTP id b19mr8854964ede.214.1552508783213; Wed, 13 Mar 2019 13:26:23 -0700 (PDT) Received: from prevas-ravi.prevas.se (ip-5-186-119-202.cgn.fibianet.dk. [5.186.119.202]) by smtp.gmail.com with ESMTPSA id m32sm940170edc.17.2019.03.13.13.26.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Mar 2019 13:26:22 -0700 (PDT) From: Rasmus Villemoes To: Pavel Machek , =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= , Jacek Anaszewski Cc: LKML , Rasmus Villemoes , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-can@vger.kernel.org, netdev@vger.kernel.org Subject: [PATCH 4/4] leds: netdev trigger: allow setting initial values in device tree Date: Wed, 13 Mar 2019 21:26:15 +0100 Message-Id: <20190313202615.22883-5-linux@rasmusvillemoes.dk> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190313202615.22883-1-linux@rasmusvillemoes.dk> References: <20190311144227.GA4404@amd> <20190313202615.22883-1-linux@rasmusvillemoes.dk> MIME-Version: 1.0 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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 in userspace. My main motivation for this is to be able to switch away from the deprecated CONFIG_CAN_LEDS, so add an example based on that and add a pointer in the net/can/Kconfig file. Signed-off-by: Rasmus Villemoes --- .../devicetree/bindings/leds/common.txt | 17 ++++++++++ drivers/leds/trigger/ledtrig-netdev.c | 31 +++++++++++++++++++ drivers/net/can/Kconfig | 3 +- 3 files changed, 50 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt index 7cb88460a47c..4f3a97e73417 100644 --- a/Documentation/devicetree/bindings/leds/common.txt +++ b/Documentation/devicetree/bindings/leds/common.txt @@ -43,6 +43,23 @@ 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, setting + linux,default-trigger = "netdev" and adding the child + node + + netdev { + rx; + tx; + link; + device-name = "can0"; + }; + + can be used to replace 'linux,default-trigger = + "can0-rxtx"' that relies on the deprecated + CONFIG_CAN_LEDS. + - led-pattern : Array of integers with default pattern for certain triggers. Each trigger may parse this property differently: - one-shot : two numbers specifying delay on and delay off (in ms), diff --git a/drivers/leds/trigger/ledtrig-netdev.c b/drivers/leds/trigger/ledtrig-netdev.c index 55153a7e8433..1f7c86df1e91 100644 --- a/drivers/leds/trigger/ledtrig-netdev.c +++ b/drivers/leds/trigger/ledtrig-netdev.c @@ -20,6 +20,7 @@ #include #include #include +#include #include #include #include "../leds.h" @@ -395,6 +396,35 @@ static void netdev_trig_work(struct work_struct *work) (atomic_read(&trigger_data->interval)*2)); } +static void netdev_trig_of_init(struct led_classdev *led_cdev, + struct led_netdev_data *trigger_data) +{ + struct device_node *np = led_cdev->dev->of_node; + const char *device_name; + + if (!np) + return; + np = of_get_child_by_name(np, "netdev"); + if (!np) + return; + + if (of_property_read_bool(np, "link")) + __set_bit(NETDEV_LED_LINK, &trigger_data->mode); + if (of_property_read_bool(np, "tx")) + __set_bit(NETDEV_LED_TX, &trigger_data->mode); + if (of_property_read_bool(np, "rx")) + __set_bit(NETDEV_LED_RX, &trigger_data->mode); + if (!of_property_read_string(np, "device-name", &device_name)) { + unsigned len = strlen(device_name); + + if (len < IFNAMSIZ) + set_device(trigger_data, device_name, len); + } + set_baseline_state(trigger_data); + + of_node_put(np); +} + static int netdev_trig_activate(struct led_classdev *led_cdev) { struct led_netdev_data *trigger_data; @@ -418,6 +448,7 @@ static int netdev_trig_activate(struct led_classdev *led_cdev) trigger_data->mode = 0; atomic_set(&trigger_data->interval, msecs_to_jiffies(50)); trigger_data->last_activity = 0; + netdev_trig_of_init(led_cdev, trigger_data); led_set_trigger_data(led_cdev, trigger_data); diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig index e0f0ad7a550a..91703a96b636 100644 --- a/drivers/net/can/Kconfig +++ b/drivers/net/can/Kconfig @@ -77,7 +77,8 @@ config CAN_LEDS # everything that this driver is doing. This is marked as broken # because it uses stuff that is intended to be changed or removed. # Please consider switching to the netdev trigger and confirm it - # fulfills your needs instead of fixing this driver. + # fulfills your needs instead of fixing this driver. See e.g. + # Documentation/devicetree/bindings/leds/common.txt depends on BROKEN select LEDS_TRIGGERS ---help---