Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp1027547ybz; Wed, 29 Apr 2020 13:41:00 -0700 (PDT) X-Google-Smtp-Source: APiQypInZRer6yEAlTOHycHJPl8HRJvBiHFF/QLMU/s6ISIYIf/G1jgZP+v/7d4rB3Sz70YO+ysp X-Received: by 2002:a17:906:1292:: with SMTP id k18mr4443737ejb.132.1588192860218; Wed, 29 Apr 2020 13:41:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588192860; cv=none; d=google.com; s=arc-20160816; b=zCYN4v/S8SJBioApHYbNZ5AqSsfdhrcFikj82aDsO79rcLk2TmxdSWVrmo3AxIbSZW a7sNf2htQrzfLBZfGuu+IK56BR5pePWF2PSc5to8lFGRkfbhJSLGGMWyXhQODUh1uM/X 0j7auBTi3+w2ykunBtbUzJTQ20/1cPIUBkDFyXAZH1omJ52xSxXBaNC+PZRJJpJnHLbK /pdJ8oVCSR5NoUPHhVYQyyrAyoAZU7bnxdFen3y2E1WTbFLYDsx8TDHcuNIuELaKrnVQ q6SxkxJEXtM9FENjZdztP+hnsqaHJ7m01gXBOcSh3epiMpA/wD+0kQiLYiNuRsB2H5+O pg/w== 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=SNYl+9ptm0p0wgOyNWYXXQzH8k/abPl+aH/5HnDHf9U=; b=TiE7Tabj9Y1mZNjhvCmx6HoLImX5Rc1jzgVWBzjxPP18K3doCLdltuWoTAzbVXYb84 4KlifhcZf3LPo6xpd/nZ+xr7BtDwre8PAaxvn/mTFqi6a4WSrrbHpQ8HoEDlmPtTIGif Ll9dNjRg18TLbAJwCPKabLBX98gKZUMxc6dXKIq+k9eThclJ4n76r7ficudYpfGuPlWF K4O4s2xkezIXVQwv/T0XNPsq6KtcRzkdsgN904wj+Byl8Q9lILIEIY5QpNTITf7REy4h Bn4I+lzV1e9yZ8j3aZj+Xfqpkex1cNd0RQ7+n7wInTvJMwKnz+h5Oj3YxwKWeQwBXn6r 4Hmg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=sX6ISd1o; 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=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gv6si4488502ejb.388.2020.04.29.13.40.36; Wed, 29 Apr 2020 13:41:00 -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; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=sX6ISd1o; 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=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727769AbgD2UhE (ORCPT + 99 others); Wed, 29 Apr 2020 16:37:04 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:54884 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727103AbgD2UhB (ORCPT ); Wed, 29 Apr 2020 16:37:01 -0400 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 03TKavRf118273; Wed, 29 Apr 2020 15:36:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1588192617; bh=SNYl+9ptm0p0wgOyNWYXXQzH8k/abPl+aH/5HnDHf9U=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=sX6ISd1o1LMltGz/f0s7y5KX9JzLZqP+M1K4/t//QFIh566WVoyHagJvgcqMbCB/1 GHCtDqimp7rKXKR9YdroyjqaO5vYB4OyMXCJDDR+9jalpnYM7zHqv1u/Dlm6xwmVcb oCQa99WCZGpMkskuly9prKbHGE5TB8pTF0qvFkCM= Received: from DFLE114.ent.ti.com (dfle114.ent.ti.com [10.64.6.35]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTP id 03TKav2Z114353; Wed, 29 Apr 2020 15:36:57 -0500 Received: from DFLE112.ent.ti.com (10.64.6.33) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Wed, 29 Apr 2020 15:36:57 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Wed, 29 Apr 2020 15:36:57 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 03TKaupI081403; Wed, 29 Apr 2020 15:36:56 -0500 From: Dan Murphy To: , CC: , , Dan Murphy Subject: [PATCH v23 03/16] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Date: Wed, 29 Apr 2020 15:28:03 -0500 Message-ID: <20200429202816.26501-4-dmurphy@ti.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200429202816.26501-1-dmurphy@ti.com> References: <20200429202816.26501-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 Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 RGB LED device driver. The LP5036/30/24/18/12/9 can control RGB LEDs individually or as part of a control bank group. These devices have the ability to adjust the mixing control for the RGB LEDs to obtain different colors independent of the overall brightness of the LED grouping. Datasheet: http://www.ti.com/lit/ds/symlink/lp5012.pdf http://www.ti.com/lit/ds/symlink/lp5024.pdf http://www.ti.com/lit/ds/symlink/lp5036.pdf Signed-off-by: Dan Murphy --- .../devicetree/bindings/leds/leds-lp50xx.yaml | 179 ++++++++++++++++++ 1 file changed, 179 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.yaml diff --git a/Documentation/devicetree/bindings/leds/leds-lp50xx.yaml b/Documentation/devicetree/bindings/leds/leds-lp50xx.yaml new file mode 100644 index 000000000000..37fadc201097 --- /dev/null +++ b/Documentation/devicetree/bindings/leds/leds-lp50xx.yaml @@ -0,0 +1,179 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/leds/leds-lp50xx.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: LED driver for LP50XX RGB LED from Texas Instruments. + +maintainers: + - Dan Murphy + +description: | + The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into + a LED group or control them individually. + + The difference in these RGB LED drivers is the number of supported RGB + modules. + + For more product information please see the link below: + http://www.ti.com/lit/ds/symlink/lp5012.pdf + http://www.ti.com/lit/ds/symlink/lp5024.pdf + http://www.ti.com/lit/ds/symlink/lp5036.pdf + +properties: + compatible: + oneOf: + - const: ti,lp5009 + - const: ti,lp5012 + - const: ti,lp5018 + - const: ti,lp5024 + - const: ti,lp5030 + - const: ti,lp5036 + + reg: + maxItems: 1 + description: + I2C slave address + lp5009/12 - 0x14, 0x15, 0x16, 0x17 + lp5018/24 - 0x28, 0x29, 0x2a, 0x2b + lp5030/36 - 0x30, 0x31, 0x32, 0x33 + + enable-gpios: + description: GPIO pin to enable/disable the device. + + vled-supply: + description: LED supply. + + child-node: + type: object + properties: + reg: + description: This is the LED module number. + + color: + description: Must be LED_COLOR_ID_MULTI + + function: + description: see Documentation/devicetree/bindings/leds/common.txt + + ti,led-bank: + description: + This property denotes the LED module numbers that will be controlled as + a single RGB cluster. Each LED module number will be controlled by a + single LED class instance. + There can only be one instance of the ti,led-bank + property for each device node. This is a required node is the LED + modules are to be backed. + $ref: /schemas/types.yaml#definitions/uint32-array + + required: + - reg + - color + - function + + grandchild-node: + type: object + properties: + reg: + description: + A single entry denoting the LED output that controls the monochrome LED. + + color: + description: + see Documentation/devicetree/bindings/leds/common.txt + + led-sources: + description: + see Documentation/devicetree/bindings/leds/common.txt + The LED outputs associated with the LED modules are defined in Table 1 + of the corresponding data sheets. + LP5009 - 3 Total RGB cluster LED outputs 0-2 + LP5012 - 4 Total RGB cluster LED outputs 0-3 + LP5018 - 6 Total RGB cluster LED outputs 0-5 + LP5024 - 8 Total RGB cluster LED outputs 0-7 + LP5030 - 10 Total RGB cluster LED outputs 0-9 + LP5036 - 12 Total RGB cluster LED outputs 0-11 + + label: + description: | + Optional node - see Documentation/devicetree/bindings/leds/common.txt + + linux,default-trigger: + description: | + Optional node - see Documentation/devicetree/bindings/leds/common.txt + + required: + - reg + - color + +required: + - compatible + - reg + +examples: + - | + #include + #include + i2c { + #address-cells = <1>; + #size-cells = <0>; + + led-controller@14 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "ti,lp5009"; + reg = <0x14>; + enable-gpios = <&gpio1 16>; + multi-led@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + color = ; + function = LED_FUNCTION_CHARGING; + + led@0 { + reg = <0>; + color = ; + }; + + led@1 { + reg = <1>; + color = ; + }; + + led@2 { + reg = <2>; + color = ; + }; + }; + multi-led@2 { + #address-cells = <1>; + #size-cells = <0>; + reg = <2>; + color = ; + function = LED_FUNCTION_STANDBY; + ti,led-bank = <2 3 5>; + + led@6 { + reg = <0x6>; + color = ; + led-sources = <6 9 15>; + }; + + led@7 { + reg = <0x7>; + color = ; + led-sources = <7 10 16>; + }; + + led@8 { + reg = <0x8>; + color = ; + led-sources = <8 11 17>; + }; + }; + }; + }; + +... -- 2.25.1