[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190314140619.3309-1-linux@rasmusvillemoes.dk>
Date: Thu, 14 Mar 2019 15:06:13 +0100
From: Rasmus Villemoes <linux@...musvillemoes.dk>
To: Pavel Machek <pavel@....cz>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Jacek Anaszewski <jacek.anaszewski@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: [PATCH v2 0/6] leds: netdev trigger: allow setting initial values in device tree
Here's a reroll of the attempt to allow initializing led_netdev_data
from DT, fixing minor bugs and inconsistensies I found while digging
into the code.
Changes in v2:
* use 0 instead of '\0' for consistency with existing code [Pavel]
* name the helper netdev_trig_set_device [Uwe]
* add a patch allowing echoing 15-character names to device_name
* ensure the length checking is done in one place [Uwe]
* drop hunk from CAN Kconfig file for now [Uwe]
* don't mention CONFIG_CAN_LEDS in device tree binding [Uwe]
* guard netdev_trig_of_init by LED_INIT_DEFAULT_TRIGGER bit [Jacek]
Rasmus Villemoes (6):
leds: netdev trigger: use memcpy in device_name_store
leds: netdev trigger: factor out middle part of device_name_store
leds: netdev trigger: move newline handling back to device_name_store
leds: netdev trigger: move name length checking to
netdev_trig_set_device
leds: netdev trigger: add documentation to leds/common.txt
leds: netdev trigger: allow setting initial values in device tree
.../devicetree/bindings/leds/common.txt | 14 ++++
drivers/leds/trigger/ledtrig-netdev.c | 68 +++++++++++++++----
2 files changed, 69 insertions(+), 13 deletions(-)
--
2.20.1
Powered by blists - more mailing lists