From patchwork Mon May 6 19:16:12 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dan Murphy X-Patchwork-Id: 163453 Delivered-To: patch@linaro.org Received: by 2002:a05:6e02:81:0:0:0:0 with SMTP id l1csp359936ilm; Mon, 6 May 2019 12:16:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqyK1qYpQDvf7ogJMF0qDE6YAnU1PDMRGK6TPoAGMMy/MHGEyqajob/1NZwb7Vzr61ki0Jo2 X-Received: by 2002:a17:902:2a:: with SMTP id 39mr34343459pla.64.1557170188657; Mon, 06 May 2019 12:16:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557170188; cv=none; d=google.com; s=arc-20160816; b=xZcqoBC7YSFw+ETBf3wZcChXTB7spL+AQQxaUPREmIXzGDCjkrtXOewemOmd4zmCk7 D3rDwWDa1QbAHHYEwblPu6N7j0O/Nvk7NaXe3MtbcXpkvgOx7nBtHDrU97EA0Au96+zu OCnIYAD1glI8HL5HlMmZY9vM0hRbux1Ug53JNO13I1ZA+dlwKMvfFqpvfxSseE0ofYcQ ydLADbtqkMWvDnhd8nBFl7N64AYg/ujq8J7Oma14De3aJ/IwQrZPY21sL0bvw1BYqMC/ nGpgVPG7zhjcP45frRxkslX3JrYja72xjw3dXYx4shg6a47eQYEFk/z6hiPBWkEJtg6I PUfQ== 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=otLfGOeGObKMgQEnDiF4xGk2Wx0tMDViixhBDAXog6o=; b=Yelk0OhoW3pkX0Knqpf69aAXIzsHsmygVI+Kmylg+c4thRQ4kCg1jDA1PhwQdmGtb1 F6OEduQou3jbH8hVzEcdNBTdAXD7U7xgt3pOycDf4+nyPVZg5YzumtIk+u59SerOSVVD wC196UDcw5aNE87GivsWyPALhvpaxZAneXntonAcQMlXNm4YAE9Vy05k3ycP4vJ+GJRy wTcYMWNR+UtoShWoaOU1UvoLc6N0XML50ZMiVQ5qhE3OCJPstZImK0OqrY90v+v+CWUz v+XaDERyLPYREsKaEUmhcZ2evx+hak3L45vvueEncc1EpI5eNFQ7BrNNWKdaLjIRaFbe iVcw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=XCmyKfKF; spf=pass (google.com: best guess record for domain of linux-leds-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-leds-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 j8si9512944pfh.239.2019.05.06.12.16.28; Mon, 06 May 2019 12:16:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-leds-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=XCmyKfKF; spf=pass (google.com: best guess record for domain of linux-leds-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-leds-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 S1726574AbfEFTQ2 (ORCPT + 1 other); Mon, 6 May 2019 15:16:28 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:52830 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726450AbfEFTQ0 (ORCPT ); Mon, 6 May 2019 15:16:26 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id x46JGAN0075440; Mon, 6 May 2019 14:16:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1557170170; bh=otLfGOeGObKMgQEnDiF4xGk2Wx0tMDViixhBDAXog6o=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=XCmyKfKF24mru4bfIDoNa5/KOE07ALrCFs0D0H/93VQRhuzi2R965DrJHy8zz1Q/9 QhQcRrpfdsUlJXDWWdSlSb/1iSngOMYZDeSuz48Vt9XvmexVtq3nfT2n9a7VktWKS0 MIN7A3ye3kV9ntKQU8L/VZtrQcvRBD62xipUt8AM= Received: from DLEE110.ent.ti.com (dlee110.ent.ti.com [157.170.170.21]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x46JGA8E092533 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 6 May 2019 14:16:10 -0500 Received: from DLEE111.ent.ti.com (157.170.170.22) by DLEE110.ent.ti.com (157.170.170.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 6 May 2019 14:16:09 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE111.ent.ti.com (157.170.170.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; Mon, 6 May 2019 14:16:09 -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 x46JG9L4090733; Mon, 6 May 2019 14:16:09 -0500 From: Dan Murphy To: , CC: , , , , Dan Murphy , Rob Herring Subject: [PATCH v4 5/7] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Date: Mon, 6 May 2019 14:16:12 -0500 Message-ID: <20190506191614.25051-6-dmurphy@ti.com> X-Mailer: git-send-email 2.21.0.5.gaeb582a983 In-Reply-To: <20190506191614.25051-1-dmurphy@ti.com> References: <20190506191614.25051-1-dmurphy@ti.com> MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-leds-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-leds@vger.kernel.org The LM3697 is a single function LED driver. The single function LED driver needs to reside in the LED directory as a dedicated LED driver and not as a MFD device. The device does have common brightness and ramp features and those can be accomodated by a TI LMU framework. The LM3697 dt binding needs to be moved from the ti-lmu.txt and a dedicated LED dt binding needs to be added. The new LM3697 LED dt binding will then reside in the Documentation/devicetree/bindings/leds directory and follow the current LED and general bindings guidelines. Reviewed-by: Rob Herring Signed-off-by: Dan Murphy --- v4 - Made assiciated ramp bindings changes and capitalization issue otherwise no change - https://lore.kernel.org/patchwork/patch/1068618/ v3 - No changes added Reviewed-by Rob - https://lore.kernel.org/patchwork/patch/1058762/ v2 - Made changes to reference ti,brightness-resolution to the ti-lmu.txt - https://lore.kernel.org/patchwork/patch/1054501/ .../devicetree/bindings/leds/leds-lm3697.txt | 73 +++++++++++++++++++ .../devicetree/bindings/mfd/ti-lmu.txt | 27 +------ 2 files changed, 74 insertions(+), 26 deletions(-) create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3697.txt -- 2.21.0.5.gaeb582a983 diff --git a/Documentation/devicetree/bindings/leds/leds-lm3697.txt b/Documentation/devicetree/bindings/leds/leds-lm3697.txt new file mode 100644 index 000000000000..63992d732959 --- /dev/null +++ b/Documentation/devicetree/bindings/leds/leds-lm3697.txt @@ -0,0 +1,73 @@ +* Texas Instruments - LM3697 Highly Efficient White LED Driver + +The LM3697 11-bit LED driver provides high- +performance backlight dimming for 1, 2, or 3 series +LED strings while delivering up to 90% efficiency. + +This device is suitable for display and keypad lighting + +Required properties: + - compatible: + "ti,lm3697" + - reg : I2C slave address + - #address-cells : 1 + - #size-cells : 0 + +Optional properties: + - enable-gpios : GPIO pin to enable/disable the device + - vled-supply : LED supply + +Required child properties: + - reg : 0 - LED is Controlled by bank A + 1 - LED is Controlled by bank B + - led-sources : Indicates which HVLED string is associated to which + control bank. This is a zero based property so + HVLED1 = 0, HVLED2 = 1, HVLED3 = 2. + Additional information is contained + in Documentation/devicetree/bindings/leds/common.txt + +Optional child properties: + - ti,brightness-resolution - see Documentation/devicetree/bindings/mfd/ti-lmu.txt + - ramp-up-us: see Documentation/devicetree/bindings/mfd/ti-lmu.txt + - ramp-down-us: see Documentation/devicetree/bindings/mfd/ti-lmu.txt + - label : see Documentation/devicetree/bindings/leds/common.txt + - linux,default-trigger : + see Documentation/devicetree/bindings/leds/common.txt + +Example: + +HVLED string 1 and 3 are controlled by control bank A and HVLED 2 string is +controlled by control bank B. + +led-controller@36 { + compatible = "ti,lm3697"; + #address-cells = <1>; + #size-cells = <0>; + reg = <0x36>; + + enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>; + vled-supply = <&vbatt>; + + led@0 { + reg = <0>; + led-sources = <0 2>; + ti,brightness-resolution = <2047>; + ramp-up-us = <5000>; + ramp-down-us = <1000>; + label = "white:first_backlight_cluster"; + linux,default-trigger = "backlight"; + }; + + led@1 { + reg = <1>; + led-sources = <1>; + ti,brightness-resolution = <255>; + ramp-up-us = <500>; + ramp-down-us = <1000>; + label = "white:second_backlight_cluster"; + linux,default-trigger = "backlight"; + }; +} + +For more product information please see the link below: +http://www.ti.com/lit/ds/symlink/lm3697.pdf diff --git a/Documentation/devicetree/bindings/mfd/ti-lmu.txt b/Documentation/devicetree/bindings/mfd/ti-lmu.txt index e3efefb194c5..782d3c9812ed 100644 --- a/Documentation/devicetree/bindings/mfd/ti-lmu.txt +++ b/Documentation/devicetree/bindings/mfd/ti-lmu.txt @@ -8,7 +8,6 @@ TI LMU driver supports lighting devices below. LM3632 Backlight and regulator LM3633 Backlight, LED and fault monitor LM3695 Backlight - LM3697 Backlight and fault monitor Required properties: - compatible: Should be one of: @@ -16,11 +15,10 @@ Required properties: "ti,lm3632" "ti,lm3633" "ti,lm3695" - "ti,lm3697" - reg: I2C slave address. 0x11 for LM3632 0x29 for LM3631 - 0x36 for LM3633, LM3697 + 0x36 for LM3633 0x63 for LM3695 Optional properties: @@ -51,7 +49,6 @@ Optional nodes: Required properties: - compatible: Should be one of: "ti,lm3633-fault-monitor" - "ti,lm3697-fault-monitor" - leds: LED properties for LM3633. Please refer to [2]. - regulators: Regulator properties for LM3631 and LM3632. Please refer to [3]. @@ -216,25 +213,3 @@ lm3695@63 { }; }; }; - -lm3697@36 { - compatible = "ti,lm3697"; - reg = <0x36>; - - enable-gpios = <&pioC 2 GPIO_ACTIVE_HIGH>; - - backlight { - compatible = "ti,lm3697-backlight"; - - lcd { - ti,brightness-resolution = <255>; - led-sources = <0 1 2>; - ramp-up-us = <200000>; - ramp-down-us = <200000>; - }; - }; - - fault-monitor { - compatible = "ti,lm3697-fault-monitor"; - }; -};