Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp2109536pxf; Sat, 27 Mar 2021 02:55:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy7n9VC8Xs5UZe3C7KhkblEY1tL3WffzdX4KCVyJlWLKkT6ErdoPW12qzCNMd8wIx4QKXHQ X-Received: by 2002:a17:907:1c1e:: with SMTP id nc30mr19855454ejc.34.1616838925123; Sat, 27 Mar 2021 02:55:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616838925; cv=none; d=google.com; s=arc-20160816; b=TBjNkuOrTALH0sLMzwuctKXIF+maZuGw0xKg6dg34QMSp241096KlqRGOXm/17FN12 cyG2PNejmEVQFqaqpPnLvNa51gHr5oEztQdXnVDuF0JONP+uGK5/LC86kDZ1DOrh1PUw FCNXtufVmMvEo3UIGBxKcjHKEgfD22wNys8OPuy7maulz/3P9LsSQ36FxxsvcVGhBG+D ClNZgHDxxsZRQUGIi+e3GODhoHLCeSMtKBxdyLb/Gaqj/hZ7z6tut+FmgkHdbcKiW7nI S/YOckvSnXE+fWsfPRnYfB97CeMdAhRuMNKPOaxqsFodB/X2z/z2swaFIB8gQPMth5Lp QTyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=V9XIq6I8w8ALE9ZoTPFt/41jCPGK8H3C0vL4oglKvKs=; b=ClcvhxyFOejuZa1HH76g7GWZ9JM+0oxThGkMQ3XBG4YBPrtu/z5sJe+kyzp8YcaB/M cWSle7IWUklMD0qcMK7TqgUx/7Nnp4t24GIpTu5P4VXXuOvHTQKRRHvdVRekOtaT5e7b ID8VDPDqnv7bqat2trG10MsJi7Mpu5oBWalrpUcVuW8nEgrvJ1Xtbo++ecoPNxRkaToQ jDvjPbmU24xH5bJquYE6jMA10WbsGJkwztJtReaf4+ZLfHu82UsOXy0EHPfPEJ7dbmw5 8i0wq9QSXT/CYvixSbjTXgg9GQKn6VxTfX451G7d5pcgIkckoUve2lVmUXitxeRmxNWt hVZA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s20si8741091edu.53.2021.03.27.02.55.02; Sat, 27 Mar 2021 02:55:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231209AbhC0JwC (ORCPT + 99 others); Sat, 27 Mar 2021 05:52:02 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:51302 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230415AbhC0Jvl (ORCPT ); Sat, 27 Mar 2021 05:51:41 -0400 Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id 12R9pEHg007154 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 27 Mar 2021 10:51:14 +0100 Received: from md1za8fc.ad001.siemens.net ([167.87.2.82]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 12R9kDOA028553; Sat, 27 Mar 2021 10:46:13 +0100 Date: Sat, 27 Mar 2021 10:46:10 +0100 From: Henning Schild To: "Enrico Weigelt, metux IT consult" Cc: Pavel Machek , Andy Shevchenko , Linux Kernel Mailing List , Linux LED Subsystem , Platform Driver , , Srikanth Krishnakar , Jan Kiszka , Gerd Haeussler , Guenter Roeck , Wim Van Sebroeck , Mark Gross , Hans de Goede Subject: Re: [PATCH v2 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs Message-ID: <20210327104610.344afebc@md1za8fc.ad001.siemens.net> In-Reply-To: <50836593-d5c9-421f-9140-2c65ac6fabe4@metux.net> References: <20210315095710.7140-1-henning.schild@siemens.com> <20210315095710.7140-3-henning.schild@siemens.com> <20210315111915.GA14857@duo.ucw.cz> <50836593-d5c9-421f-9140-2c65ac6fabe4@metux.net> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Thu, 18 Mar 2021 12:38:53 +0100 schrieb "Enrico Weigelt, metux IT consult" : > On 15.03.21 12:19, Pavel Machek wrote: > > > But I still don't like the naming. simantic-ipc: prefix is > > useless. Having 6 status leds is not good, either. > > Do we have some standard naming policy those kinds of LEDs ? There is include/dt-bindings/leds/common.h with LED_FUNCTION_* > In this case, they seem to be assigned to certain specific functions > (by physical labels on the box), so IMHO the LED names should reflect > that in some ways. The choice for "status" was because of >> /* Miscelleaus functions. Use functions above if you can. */ And those known names do not really come with an explanation of their meaning. Names like "bluetooth" seem obvious, but "activity" or "indicator" leave a lot of room for speculation. The choice in numbers was inspired by labels on the box, which i wanted to reflect in some way. Henning > There're other cases (eg. apu board familiy) that just have several > front panel leds w/o any dedication, so we can just count them up. > > > --mtx >