From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH v5 05/26] leds: core: Add support for composing LED class device names Date: Fri, 28 Jun 2019 09:46:14 +0100 Message-ID: References: <20190609190803.14815-1-jacek.anaszewski@gmail.com> <20190609190803.14815-6-jacek.anaszewski@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20190609190803.14815-6-jacek.anaszewski@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Jacek Anaszewski Cc: Linux LED Subsystem , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Pavel Machek , Rob Herring , Dmitry Torokhov , Guenter Roeck , Dan Murphy , Baolin Wang , Daniel Mack , Oleh Kravchenko , Sakari Ailus , Simon Shields List-Id: linux-leds@vger.kernel.org On Sun, Jun 9, 2019 at 8:08 PM Jacek Anaszewski wrote: > Add generic support for composing LED class device name. The newly > introduced led_compose_name() function composes device name according > to either or pattern, > depending on the configuration of initialization data. > > Backward compatibility with in-driver hard-coded LED class device > names is assured thanks to the default_label and devicename properties > of newly introduced struct led_init_data. > > In case none of the aforementioned properties was found, then, for OF > nodes, the node name is adopted for LED class device name. > > At the occassion of amending the Documentation/leds/leds-class.txt > unify spelling: colour -> color. > > Alongside these changes added is a new tool - tools/leds/get_led_device_info.sh. > The tool allows retrieving details of a LED class device's parent device, > which proves that using vendor or product name for devicename part > of LED name doesn't convey any added value since that information had been > already available in sysfs. The script performs also basic validation > of a LED class device name. > > Signed-off-by: Jacek Anaszewski > Cc: Baolin Wang > Cc: Pavel Machek > Cc: Dan Murphy > Cc: Daniel Mack > Cc: Linus Walleij > Cc: Oleh Kravchenko > Cc: Sakari Ailus > Cc: Simon Shields This is good progress on trying to bring order in chaos. A problem with LEDs is that it invites bikeshedding because it is too relateable. So by the motto "rough consensus and running code": Reviewed-by: Linus Walleij Yours, Linus Walleij