Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1630703ybp; Wed, 9 Oct 2019 17:50:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqwVjA3aPENuDaB0LXhB+6kcDQxHfbkvueXayT+qGq3Ty2WKUDP/3rh562OyUs63zP8gD0pN X-Received: by 2002:aa7:c38f:: with SMTP id k15mr5742402edq.100.1570668623529; Wed, 09 Oct 2019 17:50:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570668623; cv=none; d=google.com; s=arc-20160816; b=qRtlV/LqZ04traz1eYM6kTkQ9dp6qNqRHuOGPJK7Bg0QKetoe78Z0+rX8okf4SZo30 +B6pWArYN3sTg9kvamxyENznsoDnCR/NqIj12hT4M0bd2RyKG4M7dgnedCJVvia1HU9c Rs9UQQgSmMpMqRCVFQ9YLd1zDc6Z+wkNiE4EjlIse3RkgoKd95Hu8TWu6l+FPKqsh6Jq 8+LF/HBFXE2M6V5Fj+avlg+x1+rlV+GvM/UlnfOY6d7bHoAmQc5bgVz2X5MPxcIhqD7N 2vxVAEGvB9QO/s41W4f/xemgB8VCQXCM/EUfUN5Imyn+PHMLVtLDoA7pps3iF28icnLp kKuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=bXA+tWGCPIN3ZK9prxHVq3q3UctX1VVbNkAauQN1QlE=; b=IhE+54BfKbye/k2zoKskwv4omFtomF+P+3swPLUwrGCvXGd67IoZd6vZAxGTZOTb0E gLiqCexyMs/EmALHZbcB5IwsyXoAsUdvGsv9x6HCFZFNTKy+6v+cKP9F6sWns2rIHcp9 os3vlaxa2KmNgCCKMycVcjgtlFZ77HbmLF8yOXNyu58UdC8Tg04NQeZZ4TZNx3FvcR2P gbZSdtlu0D9nCjplYZw35jj+IUQ8QDEt+oVs5CutESguxtQjPgDTuxc8QvPZ1fC4AEba Tb4SbFPyxqykrn6+6k96Qu/D1dX1njogQ/Ln0JxzX5GR8bcaLqasytVyhITub9xeSX++ 5Q6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=ZXwkh4Yf; 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 j18si2058007ejv.201.2019.10.09.17.50.00; Wed, 09 Oct 2019 17:50:23 -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=ZXwkh4Yf; 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 S1732476AbfJJAtk (ORCPT + 99 others); Wed, 9 Oct 2019 20:49:40 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:41774 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731230AbfJJAtk (ORCPT ); Wed, 9 Oct 2019 20:49:40 -0400 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id x9A0nb3J119893; Wed, 9 Oct 2019 19:49:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1570668577; bh=bXA+tWGCPIN3ZK9prxHVq3q3UctX1VVbNkAauQN1QlE=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=ZXwkh4YfUWIIRkL0XwHCuU2dFC+0WKHbLoT9m9+J641lep4CDaqJcw3ZMJZQofPbL ibZN8tQlF7vuiPZpkF7IQPRZEdokx0l6Q3npFoiXNsYdXwwN3y4q+VfNvqyOk8DThC rLuu9UHx97PXDa1yzk5jB0/MFYrgwK+exoZAJKdI= Received: from DFLE100.ent.ti.com (dfle100.ent.ti.com [10.64.6.21]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x9A0nbtU111924 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 9 Oct 2019 19:49:37 -0500 Received: from DFLE101.ent.ti.com (10.64.6.22) by DFLE100.ent.ti.com (10.64.6.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 9 Oct 2019 19:49:33 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE101.ent.ti.com (10.64.6.22) 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; Wed, 9 Oct 2019 19:49:36 -0500 Received: from [10.250.65.13] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id x9A0na8n030203; Wed, 9 Oct 2019 19:49:36 -0500 Subject: Re: [PATCH v11 01/16] dt: bindings: Add multicolor class dt bindings documention To: Jacek Anaszewski , CC: , References: <20191008204800.19870-1-dmurphy@ti.com> <20191008204800.19870-2-dmurphy@ti.com> <487f2425-1570-c946-c4a6-3da60ad21f2c@gmail.com> From: Dan Murphy Message-ID: Date: Wed, 9 Oct 2019 19:49:17 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <487f2425-1570-c946-c4a6-3da60ad21f2c@gmail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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 Jacek On 10/9/19 5:07 PM, Jacek Anaszewski wrote: > Dan, > > On 10/8/19 10:47 PM, Dan Murphy wrote: >> Add DT bindings for the LEDs multicolor class framework. >> >> Signed-off-by: Dan Murphy >> --- >> .../bindings/leds/leds-class-multicolor.txt | 98 +++++++++++++++++++ >> 1 file changed, 98 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.txt >> >> diff --git a/Documentation/devicetree/bindings/leds/leds-class-multicolor.txt b/Documentation/devicetree/bindings/leds/leds-class-multicolor.txt >> new file mode 100644 >> index 000000000000..8619c9bf1811 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/leds/leds-class-multicolor.txt >> @@ -0,0 +1,98 @@ >> +* Multicolor LED properties >> + >> +Bindings for multi color LEDs show how to describe current outputs of >> +either integrated multi-color LED elements (like RGB, RGBW, RGBWA-UV >> +etc.) or standalone LEDs, to achieve logically grouped multi-color LED >> +modules. This is achieved by adding multi-led nodes layer to the >> +monochrome LED bindings. >> + >> +The nodes and properties defined in this document are unique to the multicolor >> +LED class. Common LED nodes and properties are inherited from the common.txt >> +within this documentation directory. >> + >> +Required LED Child properties: > s/Child/child/ Ack > >> + - color : For multicolor LED support this property should be defined as >> + LED_COLOR_ID_MULTI and further definition can be found in >> + include/linux/leds/common.h. >> + >> +led-controller@30 { >> + #address-cells = <1>; >> + #size-cells = <0>; >> + compatible = "ti,lp5024"; >> + reg = <0x29>; >> + >> + multi-led@1 { >> + #address-cells = <1>; >> + #size-cells = <0>; >> + reg = <1>; >> + color = ; >> + function = LED_FUNCTION_STATUS; > Status is not too fancy function for multi color LED ;-) > I'd skip it entirely for this example if we don't have > anything suitable at the moment for our disposal. Not sure I understand.  Status is a good example as a RGB module can be used to present charging status Unless I misinterpreted your comment. Dan