From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EBD33CA9EC4 for ; Wed, 30 Oct 2019 09:01:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C2F5220663 for ; Wed, 30 Oct 2019 09:01:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="SNIJd0jr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726584AbfJ3JB6 (ORCPT ); Wed, 30 Oct 2019 05:01:58 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:37362 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726526AbfJ3JB6 (ORCPT ); Wed, 30 Oct 2019 05:01:58 -0400 Received: by mail-pl1-f195.google.com with SMTP id p13so695365pll.4 for ; Wed, 30 Oct 2019 02:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=m5azgLhd2I2E3q9JQtIgUVQ0suPVCkYbQEeRBm5oMb8=; b=SNIJd0jrHsBMX6/ZKZfmY+w36WI2FQ8qqZCU7AAOSX1m1BH+waTBtt4HsR5Cpitl0M qizjCUyqfRXUfN6QTVJOMhqIJjxSn2xIGAaLdkeydUjLLMvQqr564H7wMctcKfSwSKhI 34pcDje4oDfteKOd0sOIWEPkpGduCiO9uBJes8AEfdXJj//H+RJxVEhKME1VjEfcglcv bQtYVMecgFVUuv8CqgXp3WMq/wv1mpqGjiGcc+F8WXGpzrls96q4j9uVNmvQtTjNZqOy xRH30D1vP/r22R/QtbgSOmLCKl/U61AlaG9mLcczOCemky44THQcAFq/cMwg0aH4OZ4p j7dQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=m5azgLhd2I2E3q9JQtIgUVQ0suPVCkYbQEeRBm5oMb8=; b=ThrIprzM7+SGwkCHD307UWzAa6HDkNdZ0z7+pFfVl2jfaKSkVH3e2uKlZWtz8PzJp+ DyxYrDuFpqxZ6HXzw3wOzG5rjo+UuFqPGeh8zeVXIE/Qf8sGSSc1RPs4HgBZoHDLMXfo PjiOPoJlsUVOR2/Tj0jRCD7eenaeZ8QcsU29aNXR2pYXx20QmYcpLfY2U4vcGp4qFZgy Mlzz2+s7Tx5f1L7RsupC0l9W3c64QkRxtAsHXBiBbmy9nUGkQXlHX5esIFlPpoAbyL/+ kn846WU1CsRtC4GkvXkuYkXgoSio7LzPjDJa6Mpp5rRtaBsN+OvCXepIQI90ACMZlmA3 oJSw== X-Gm-Message-State: APjAAAXHaDySFcTIQ68u5Sg6Y1JSmHfn5Te9Wd+IoxlFpc3R1894pH53 Vv6VkMmNvbHLqkzs2KE47h3X X-Google-Smtp-Source: APXvYqx1+RxRWncZTcuyUZhz6kgWlf5fD+XfO4AMeFborkT4X05rfAgRFXHGr0HdkiWpGhfJT+G4fg== X-Received: by 2002:a17:902:d891:: with SMTP id b17mr3445548plz.310.1572426117078; Wed, 30 Oct 2019 02:01:57 -0700 (PDT) Received: from localhost.localdomain ([2409:4072:618e:77d9:c9fa:423a:3851:8df4]) by smtp.gmail.com with ESMTPSA id g24sm2070351pfi.81.2019.10.30.02.01.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Oct 2019 02:01:56 -0700 (PDT) From: Manivannan Sadhasivam To: shawnguo@kernel.org, s.hauer@pengutronix.de, robh+dt@kernel.org Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, darshak.patel@einfochips.com, prajose.john@einfochips.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Manivannan Sadhasivam , Jacek Anaszewski , Pavel Machek , Dan Murphy , linux-leds@vger.kernel.org Subject: [PATCH v2 1/4] dt-bindings: leds: Document commonly used LED triggers Date: Wed, 30 Oct 2019 14:31:21 +0530 Message-Id: <20191030090124.24900-2-manivannan.sadhasivam@linaro.org> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20191030090124.24900-1-manivannan.sadhasivam@linaro.org> References: <20191030090124.24900-1-manivannan.sadhasivam@linaro.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This commit documents the LED triggers used commonly in the SoCs. Not all triggers are documented as some of them are very application specific. Most of the triggers documented here are currently used in devicetrees of many SoCs. Cc: Jacek Anaszewski Cc: Pavel Machek Cc: Dan Murphy Cc: linux-leds@vger.kernel.org Signed-off-by: Manivannan Sadhasivam --- .../devicetree/bindings/leds/common.txt | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt index 9fa6f9795d50..2a6806161590 100644 --- a/Documentation/devicetree/bindings/leds/common.txt +++ b/Documentation/devicetree/bindings/leds/common.txt @@ -55,6 +55,23 @@ Optional properties for child nodes: "timer" - LED flashes at a fixed, configurable rate "pattern" - LED alters the brightness for the specified duration with one software timer (requires "led-pattern" property) + "mmc[N]" - LED indicates [N]th MMC storage activity + "flash" - LED indicates camera flash state + "torch" - LED indicates camera torch state + "audio-mute" - LED indicates audio mute state + "audio-micmute" - LED indicates mic mute state + "bluetooth-power" - LED indicates bluetooth power state + "usb-gadget" - LED indicates USB gadget activity + "usb-host" - LED indicates USB host activity + "mtd" - LED indicates MTD memory activity + "nand-disk" - LED indicates NAND memory activity (deprecated), + in new implementations use "mtd" + "disk-read" - LED indicates disk read activity + "disk-write" - LED indicates disk write activity + "none" - No trigger assigned to the LED. This is the default mode + if trigger is absent + "cpu" - LED indicates activity of all CPUs + "cpu[N]" - LED indicates activity of [N]th CPU - led-pattern : Array of integers with default pattern for certain triggers. Each trigger may parse this property differently: -- 2.17.1