Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2192157ybm; Thu, 23 May 2019 12:53:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqxntnu81pMc1/puI+GK2YSPlvodH0FsWCi2x/hfA2O/+AUjIb515apd42TjuJOJ1s/WOtMk X-Received: by 2002:a17:902:b106:: with SMTP id q6mr47162503plr.215.1558641225536; Thu, 23 May 2019 12:53:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558641225; cv=none; d=google.com; s=arc-20160816; b=XsJpFskR6vs/Z4If5+0Qo+rUjgwMu5YpVaEqdNkTYcsHh5cpQpQ3MGU7492xPgmqoa suC8J3ED5CNK5pvmKbahFFYOOgGq13sfFDPx0x+MsmwATCXfPC8GDHTpSICcAjNu76zN 7evW8wwd8yAeG7t/Svy8wXU5+3OW4i1JFB1RI19FASfQJNSF/NM+ZebpzLy40KxjApwW 1EdNWlo/rHSzDuFNCj2MgcKdykY8Q+7xxItKsMF9PJh14l9BBtC61i5OTJhGmjoJajea uOE5oCJhQ0qVBJm87cbHJWQWfXjn6DuwpmLwnplwEK7Awl262rkAZZPzNBziZ6XKlEu+ H21g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=n5ieitO5auRi1g1b8vCdK13uEPku9s5t3nKY1zvO/Yw=; b=kvO9R4qgSid3NI77Vx0sSKOM4citAEUTk/DJrzsYjJRLqWOwmJouK8L0X2gMvRNFA6 xqsRBcbGJZBkKi+4yIjj5L540uwXO1NlKWhSn2Wi43v2LiVKE5V+e4fMSWsh7/8X5YY0 /5z1qd53KPJJTxvsUbhToQqlH0lvyrs5Y1Dw4qa8X/oxnTRPkBwnG2e3DkzjIx3WkN7T 8YU3SSeRPcmYTtTI73+fdPYTBKWPpN13pgfPtIQxbW6uEc/W9eLKRxM9+ToLIUNJpvss +yjsM1c2ZVXSrXUvpHcFj1HI1pu1tfNwbo5YUsWG+5CYQmnmjDQ5c9q++1GMrGPeZOWE lrvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=na7fkr11; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a5si548537pff.97.2019.05.23.12.53.30; Thu, 23 May 2019 12:53:45 -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=@ti.com header.s=ti-com-17Q1 header.b=na7fkr11; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387762AbfEWTv3 (ORCPT + 99 others); Thu, 23 May 2019 15:51:29 -0400 Received: from lelv0143.ext.ti.com ([198.47.23.248]:52944 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731851AbfEWTIn (ORCPT ); Thu, 23 May 2019 15:08:43 -0400 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id x4NJ8bbb065636; Thu, 23 May 2019 14:08:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1558638517; bh=n5ieitO5auRi1g1b8vCdK13uEPku9s5t3nKY1zvO/Yw=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=na7fkr11Rn6UB3EO9U942sFWrZu6vUo0tmOteQUSanT/3EeJ9sOXqyp6rqVf7VzJe Dem44kmCiMlzpetcur+HFkfPn2qjER4BluFP1QCdpq87xLHl3bB9LiYPy4YxgYbx2P YbQMx7Nr2qM1j06IqFxndgjZo6BD3nwZZjFZ5/sE= Received: from DFLE108.ent.ti.com (dfle108.ent.ti.com [10.64.6.29]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x4NJ8bB6043180 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 23 May 2019 14:08:37 -0500 Received: from DFLE111.ent.ti.com (10.64.6.32) by DFLE108.ent.ti.com (10.64.6.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 23 May 2019 14:08:36 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE111.ent.ti.com (10.64.6.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Thu, 23 May 2019 14:08:36 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id x4NJ8aNL071426; Thu, 23 May 2019 14:08:36 -0500 From: Dan Murphy To: , , CC: , , , Dan Murphy Subject: [PATCH v3 1/9] leds: multicolor: Add sysfs interface definition Date: Thu, 23 May 2019 14:08:12 -0500 Message-ID: <20190523190820.29375-2-dmurphy@ti.com> X-Mailer: git-send-email 2.21.0.5.gaeb582a983 In-Reply-To: <20190523190820.29375-1-dmurphy@ti.com> References: <20190523190820.29375-1-dmurphy@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add a documentation of LED Multicolor LED class specific sysfs attributes. Signed-off-by: Dan Murphy --- .../ABI/testing/sysfs-class-led-multicolor | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor diff --git a/Documentation/ABI/testing/sysfs-class-led-multicolor b/Documentation/ABI/testing/sysfs-class-led-multicolor new file mode 100644 index 000000000000..2f102ede258b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-multicolor @@ -0,0 +1,57 @@ +What: /sys/class/leds//colors/sync_enable +Date: April 2019 +KernelVersion: 5.2 +Contact: Dan Murphy +Description: read/write + Writing a 1 to this file will enable the synchronization of all + the defined color LEDs within the LED node. Brightness values + for each LED will be stored and written when sync is set to 1. + Writing a 0 to this file will disable syncing and allow + individual control of the LEDs brightness settings. + +What: /sys/class/leds//colors/sync +Date: April 2019 +KernelVersion: 5.2 +Contact: Dan Murphy +Description: write only + Writing a 1 to this file while sync_enable is set to 1 will + write the current brightness values to all defined LEDs within + the LED node. All LEDs defined will be configured based + on the brightness that has been requested. + + If sync_enable is set to 0 then writing a 1 to sync has no + affect on the LEDs. + +What: /sys/class/leds//colors//brightness +Date: April 2019 +KernelVersion: 5.2 +Contact: Dan Murphy +Description: read/write + The led_color directory is dynamically created based on the + colors defined by the registrar of the class. + The led_color can be but not limited to red, green, blue, + white, amber, yellow and violet. Drivers can also declare a + LED color for presentation. There is one directory per color + presented. The brightness file is created under each + led_color directory and controls the individual LED color + setting. + + If sync is enabled then writing the brightness value of the LED + is deferred until a 1 is written to + /sys/class/leds//color/sync. If syncing is + disabled then the LED brightness value will be written + immediately to the LED driver. + + The value of the color is from 0 to + /sys/class/leds//colors//max_brightness. + +What: /sys/class/leds//colors//max_brightness +Date: April 2019 +KernelVersion: 5.2 +Contact: Dan Murphy +Description: read only + Maximum brightness level for the LED color, default is + 255 (LED_FULL). + + If the LED does not support different brightness levels, this + should be 1. -- 2.21.0.5.gaeb582a983