Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1584901pxb; Thu, 4 Mar 2021 15:30:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJwMRhgbjN2CzO0tX1qUdRal1T6aV9Ov9q84iRlB/g4YIn5SHoD+a19LP8nyn6PLTCeUIxVz X-Received: by 2002:a50:eb97:: with SMTP id y23mr6939016edr.170.1614900650539; Thu, 04 Mar 2021 15:30:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614900650; cv=none; d=google.com; s=arc-20160816; b=OpJp7KoHq30ywX1U8kg0CM+uQhMDd3NONrhYMes3n4T/JUKp0k3EDnG9+gfin05lhU Qscsmfd6zsrN7m/Us2Hbhu6uykNw5xJn3teJuPWicXs6qzgjBiu7c3ntNKAS227Zf0eX veSbvzVwgkU8NC7tGIGYFEUsK4sgGDURm/BPKE9NtLVoLYqdDsye4esOiVSa+AiovZPn LEDKjqWrqmdMZLplWzwi7/vlEJNhrFJapASacV5vFXEzf6KpviFssTQoy9hLULghiRwg tVRTVTX00Yej7C0TWDDoKV15tzmosp9In/IYS7/k6a5TDpKPCb69QnmX2EXP29Rxkhn9 mf7g== 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=zT3ctu4tS09W3AJno2fxp1pL2YU9nz0xl2EmGSgyBUs=; b=E1bddxolGvpjfrM1KWcuq51nx6LXJcOpafkI6Npasj/O2BlhucleeCeBGeHdoFY3Nm SnotaIm0t94hl8rrIhARuoW9uQrLzxQYhftQIPr2qGKz/e9XoOCRRQGyMEkkpxl666eY SolTcohMLfX5xE/u04kyLmsVriZnxTT4DYETslbpH+XVuU9l6SAkfGyW5hB58kuegjh6 +13ni0KzNntH9cnBSknLh3sIwPi46D0n7JOz20VnQxJL2nR7Byj5synXZJUpoTYProkZ zro1yfNjY7qif6/Bkc46EV3r1wQpjsLNtDjUQGw0NapK3+4/Ib27alpb9+CiynfIAvjX l/yg== 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 t18si545119edr.399.2021.03.04.15.30.25; Thu, 04 Mar 2021 15:30:50 -0800 (PST) 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 S1353831AbhCDAGG (ORCPT + 99 others); Wed, 3 Mar 2021 19:06:06 -0500 Received: from lizzard.sbs.de ([194.138.37.39]:35476 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1388063AbhCCUta (ORCPT ); Wed, 3 Mar 2021 15:49:30 -0500 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 123KmOxH011929 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Mar 2021 21:48:24 +0100 Received: from md1za8fc.ad001.siemens.net ([139.22.36.86]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 123KmNG7020262; Wed, 3 Mar 2021 21:48:23 +0100 Date: Wed, 3 Mar 2021 21:48:21 +0100 From: Henning Schild To: Pavel Machek Cc: , , , , Srikanth Krishnakar , Jan Kiszka , Gerd Haeussler , Guenter Roeck , Wim Van Sebroeck , Mark Gross , Hans de Goede Subject: Re: [PATCH 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs Message-ID: <20210303214810.511ad65a@md1za8fc.ad001.siemens.net> In-Reply-To: <20210303193134.GB8720@amd> References: <20210302163309.25528-1-henning.schild@siemens.com> <20210302163309.25528-3-henning.schild@siemens.com> <20210302205452.GA32573@duo.ucw.cz> <20210303141052.30641e6b@md1za8fc.ad001.siemens.net> <20210303193134.GB8720@amd> 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 Wed, 3 Mar 2021 20:31:34 +0100 schrieb Pavel Machek : > Hi! > > > > > +static struct simatic_ipc_led simatic_ipc_leds_io[] = { > > > > + {1 << 15, "simatic-ipc:green:run-stop"}, > > > > + {1 << 7, "simatic-ipc:yellow:run-stop"}, > > > > + {1 << 14, "simatic-ipc:red:error"}, > > > > + {1 << 6, "simatic-ipc:yellow:error"}, > > > > + {1 << 13, "simatic-ipc:red:maint"}, > > > > + {1 << 5, "simatic-ipc:yellow:maint"}, > > > > + {0, ""}, > > > > +}; > > > > > > Please use names consistent with other systems, this is user > > > visible. If you have two-color power led, it should be > > > :green:power... See include/dt-bindings/leds/common.h . > > > > Well we wanted to pick names that are printed on the devices and > > would like to stick to those. Has been a discussion ... > > Can we have symlinks to have multiple names per LED? > > No symlinks. We plan to have command line tool to manipulate LEDs, > aliases might be possible there. Sounds like a future plan. sysfs and "cat" "echo" are mighty tools and "everything is a file" is the best idea ever. So i would say any aliasing should live in the kernel, but that is just me. Tools will just get out of sync, be missing in busybox or a random yocto ... or whichever distro you like. On the other hand you have "complexity should be userland" ... i do not have the answer. > > How strong would you feel about us using our names? > > Strongly. :-) OK, will try to find a match where possible. > Do you have a picture how the leds look like? I could even find chassis photos in our internal review but that would be too much. Our idea is probably the same as yours. We want the same names across all devices. But we struggle with colors because on some boxes we have red+green, while other offer yellow ... implemented in HW and messing with red+green in some cases. But so far we only looked at Siemens devices and thought we could get our own "namespace". To be honest i could not even tell how our names map on the known ones, but we will do our best to find a match. They all are "high-level" so "power" and other basic things are not exposed. regards, Henning > Best regards, > Pavel