Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp3042785ybd; Fri, 28 Jun 2019 01:47:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqx+ediKa1OIWZd8qhOv+xVA+Lt8XKFKp6V48rDVVOAW1XCQElRD7M0JiZ1F6Wgt6jYpBNd7 X-Received: by 2002:a17:902:724:: with SMTP id 33mr9930921pli.49.1561711620983; Fri, 28 Jun 2019 01:47:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561711620; cv=none; d=google.com; s=arc-20160816; b=ALo1YZOZk1rG3urxDbUrktJCTfGh6s4SAwMaeO8evD7HZJPxN9b+rIP3p/EMJZEt/1 ACvjWI83LKQn2TkdonxV+0pqijAiJk3R1e0/ZOKvT9SiSMLkn68VAeVzLbaJD5Ed4ZT0 BrNoWIo3mzcCDEzK7jVK4MUZ+0Rmxu6+tsufUfudx0u91jPSVS572lahK39a1jvLlj7s 8Qu/ae5jlGp8Q1BL9PNjkaRrm/XxqRt+l5hmxlX04bhwZGCHBJLPAQbO0tOVjiUPA1lu pkBG7yo7Oz1zwaYjyr2+OPqNr9lnelXY1oRTYn7UBNo8T5TWktLq856S76CSl8KMWGzu FpIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=lQNaKSJYVO+SBfhaRTd+ObgB+axwBGKUKZwAi5fi5AM=; b=R1AA0TdAy5cfNmaQMvxE0LU0dEU4hzz6ccoS2hbTF28K5VsXsKxgh6V3eBAiwpMO2/ rGHvw39WVPOj6KauZ3WpfPOKAUWx//DZ8cffJNrw0mjAd80kZT/unMO7LdcEs2byr/Do Z9JN+6znzfvZ3ZzwbbUqar5TzBmni2/1ryoTNppql4ge8rxVYahZkMNeLp1fvx5CMDsV g0Lf1xJer+wX2QDx9LU0QRZ5LsW+dcWfY51Mtww0qmk1D2htNbL6jNYmQr3CfOzao2yK Cgehj18wKrA5x2ilDYqU+s5BjGwUrGr6buNlvcLTrMDDokxwvN7W73l8pZVSsLbMDCfs dcQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=LpBzdV3D; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y8si1747332pgq.134.2019.06.28.01.46.44; Fri, 28 Jun 2019 01:47:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=LpBzdV3D; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726542AbfF1Iq2 (ORCPT + 99 others); Fri, 28 Jun 2019 04:46:28 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]:42575 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726426AbfF1Iq2 (ORCPT ); Fri, 28 Jun 2019 04:46:28 -0400 Received: by mail-lj1-f196.google.com with SMTP id t28so5154014lje.9 for ; Fri, 28 Jun 2019 01:46:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lQNaKSJYVO+SBfhaRTd+ObgB+axwBGKUKZwAi5fi5AM=; b=LpBzdV3DdCgI12TYlbjXRnT2CgY9b7ToRmHBIC2H6bjhKPSz1XhedsQivDv9ZCFlo0 x/RZj+DG0L5MS7QwKo3vx9AB0bQVZKUyDvM1d4RLV65hkoRS07x50oEqd56ghXPp1aMT yc1Aml6llp192DO7H7nz5YU1Og/Li6VqEtg9Iix/DA7kNYY41wrxANScMvWiC+w1gpLG HKWDL/E1p8OlH9CEwDjU9sGQ0pVe8gu7TuscxNRFR9aLJzwrt4s22+9mUBiS5pPxe3N4 ZWjO0mJ3TwID3DKeegQDd49Yw69IOT4Apurk7LWuwnDk3KxZQsPNrOreu0yGYjcsEqyt hRNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lQNaKSJYVO+SBfhaRTd+ObgB+axwBGKUKZwAi5fi5AM=; b=KdKR0ncDXTmwOYt+5q/mKe9N1i82gsSeYvtW5BPMOErGyydo/dzlS7bcYfTTKvJ5rZ SyFS9aahyjnkVwXmGhP0qg5xnmggoJ768lgnzjLIsJkFah5xMEnef6OGCJyAeILZtuyI j/m22QrGRwL6LqTpX7d4mUlaWjWw8rti2qAWgS8B6NeAsSLBza+a+ga1bUyOZZupseYa CP/C1sniCbn9RBJWU5vcZMEPot7/IMW1gyFO6qQINUNewvQdSyGt/Rq9z0P9fJSVON0M Nx6B+LzPQxgI+QB7qSxn7g3TiY4ZehRhChwAXw6/DvVeTdierF2pnwoBFwgONPqAdre6 rj3g== X-Gm-Message-State: APjAAAWo8wny8v+Lv8qEYdLpzQup7Lmy4JXNEU+ISS74Xz+OLorXagfh 0OeB0uSAaaZf5t09AHjBik+9CT8XEEJzr8HsVWP/Ng== X-Received: by 2002:a2e:2c14:: with SMTP id s20mr5415213ljs.54.1561711586591; Fri, 28 Jun 2019 01:46:26 -0700 (PDT) MIME-Version: 1.0 References: <20190609190803.14815-1-jacek.anaszewski@gmail.com> <20190609190803.14815-6-jacek.anaszewski@gmail.com> In-Reply-To: <20190609190803.14815-6-jacek.anaszewski@gmail.com> From: Linus Walleij Date: Fri, 28 Jun 2019 09:46:14 +0100 Message-ID: Subject: Re: [PATCH v5 05/26] leds: core: Add support for composing LED class device names 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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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