Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp577533ybz; Fri, 24 Apr 2020 05:47:01 -0700 (PDT) X-Google-Smtp-Source: APiQypLD4gXjwVThRONGm31HA5jsevP9AFWc29Uj0c/vzpJBy1PDOkIxBt8mNV29v0Af4/CzWIvN X-Received: by 2002:a50:8e4b:: with SMTP id 11mr6745862edx.329.1587732421254; Fri, 24 Apr 2020 05:47:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587732421; cv=none; d=google.com; s=arc-20160816; b=h3fyKT58E1jkzuVlbT3ghGpmJco48L7JxiLBtND6S4Hw76ODb/tg2i/B5gtdm8dmZ3 XypFm5CQHs6ng8+dhnnG+Hk/qVrth0zQqi4xCjsmJI5tdB9lJLz5yhoFq8HcdoP2VmNM ZxTlk+/aXAY6L1YABn4InWcWpZbAVtppqKfUeakPVuxW9KYnKvb8rzSbj2PHpvBTo/fT lNaqVR7H6dOXh+u5OlFALyl3JUsCsAeDVW7Lyns4Cv0p/f9v0gGA8zN0JqxxiH2LzidA yVMW4k4YtSbkM2MzgguGP44Mz2e4LxMOwZKpOXtdmPJqdODzZB7bs1DCoxYyIs9xq3jq RRrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=b961e3N0Bl86PcpBFkUfEW/0PHLnIXoujr1K39uVuyU=; b=mcp0Myn8/XaS2e6EGP6t8AhzzilhvhxcYRfniaT39jHKZiqWtIMQf7AhkATUPBCdm3 QCXNBxlL2R7/U2AG/0xE5aUhiCcn99/3AJIfyydQWdJDPDMIRMzjqxuy5Wr7ixu9llWE Wx7ljj2bJ4Ckxvk4bIkkPBivwZYZ/9GhY8UobCVeIMcKfsRfhhJ+nhHZ6SknPCPNxXDB QiLXn6jCyy91bukG+aUNrNO925HxVC+3jm1tNu2kmrzfgq8K2PzQaFFPND/XMRuQvA7w sLvw8Pm1N3/i4/LwunmDG6aF97L1RCK3AgND5y2yG3zCQwnHVwZrixT+WR8IQVqDpXX9 2Mug== 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=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c9si2981596edt.576.2020.04.24.05.46.37; Fri, 24 Apr 2020 05:47:01 -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=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727830AbgDXMoa (ORCPT + 99 others); Fri, 24 Apr 2020 08:44:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726959AbgDXMo3 (ORCPT ); Fri, 24 Apr 2020 08:44:29 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AC16AC09B045; Fri, 24 Apr 2020 05:44:29 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: sre) with ESMTPSA id 277442A2C16 Received: by earth.universe (Postfix, from userid 1000) id 7724E3C08C7; Fri, 24 Apr 2020 14:44:23 +0200 (CEST) Date: Fri, 24 Apr 2020 14:44:23 +0200 From: Sebastian Reichel To: Pavel Machek Cc: Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com, Ian Ray , Samu Nuutamo Subject: Re: [PATCH] ARM: dts: imx53: ppd: alarm LEDs use kernel LED interface Message-ID: <20200424124423.jo25ai5oifvalgpr@earth.universe> References: <20200416145123.73039-1-sebastian.reichel@collabora.com> <20200424093226.GB2647@amd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7nkxbfnqehgw6jzh" Content-Disposition: inline In-Reply-To: <20200424093226.GB2647@amd> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --7nkxbfnqehgw6jzh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Apr 24, 2020 at 11:32:26AM +0200, Pavel Machek wrote: > On Thu 2020-04-16 16:51:23, Sebastian Reichel wrote: > > From: Ian Ray > >=20 > > Use kernel LED interface for the alarm LEDs. >=20 > Could we get these changes cced to LED maintainers? Sorry, you are not turning up via get_maintainer.pl and usually subsystem maintainers are not CC'd for every DT device instance. E.g. I do not want to be always CC'd for DT board file containing a battery/charger. I'm quite surprised you want to be CC'd for them, just looking at ARM DT files there are over 1000 instances of leds. > > + alarm1 { > > + label =3D "alarm:red"; > > + gpios =3D <&gpio7 3 GPIO_ACTIVE_HIGH>; > > + }; >=20 > So... What is function of these leds, and can we get naming more > consistent with rest of the kernel? The device is a medical patient monitor and these are alarm LEDs informing about critical device or patient status. They are referenced by their color (those are discrete LEDs, not a multi-color one) basically everywhere. The only exception is "silenced", which means that audible alarm is surpressed. I don't think we have something comparable for any of those LEDs in the mainline tree. -- Sebastian --7nkxbfnqehgw6jzh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAl6i3yAACgkQ2O7X88g7 +pryFQ/+LLmFpwKTRHZWtfoNa5Ki7MK+Xdk9+ZihxLOvlDA1RDD4mliuR3DYnWUi G/ahfBFFXavkGkbLH1EOXUiG4I0vgpKhL8noAprz6mH+YHt5qJ2d9rT8VlzPnfjx cpy1jHcQI/o/KLhf2E5vcGLrekYbsRKAz1zRNBvULVopDTftliJnntUrB4epZUNH 5c7/R8RaqNuJ4s2YUW8KG0w9Pbe2SuWMBlAYdQQ+15m3TCgmt4MQssKsBVlCemSz fpnCHqi+e6oeaL5EFyhfad2ndFppNcIvc+fc7VP/cHUIb/C8Szsj+Bj8O2BAME0K zwTdeeJ/wv8F5b2CunIi+lbZj3vo1+NraBTlYmrOwp8i9B6lcl25NoWez1XLsld2 XLCe+WwfU1UOVRoCBKm5khL7Ssd0hm5aDpc5R20Fxi7tqRi/BynYg96vkskHRzXq cYTbSj/DwAknw3EeAshJzpwycl5Q+3h3aTIcpJ/JYRnB6GIzV5/KbZSDR3AYGXHT oyGtFdcA6MYOluOEk0tU2cRb32lH62//vmNSHSHrIIE3hHp+/6rfGvXSEnqV3i82 w92tnIFXr7R4KYKyOmarSQpFxJ+UV+51hF2kOe6UbokEuYCHd4SuASXMCrpmjqrf oIJULpENjHtbA8utSZMhIkmovy2lwXQ8h+X4/Cii14a2loJNyyU= =8oog -----END PGP SIGNATURE----- --7nkxbfnqehgw6jzh--