Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1308543imm; Wed, 8 Aug 2018 14:42:42 -0700 (PDT) X-Google-Smtp-Source: AA+uWPxDspfyXv6yLFF9Re6S/2KWHy1EIELELtBhI3U1E4vXV3wvlYS4t4x3eNyIUdBKLbtPJS2X X-Received: by 2002:a63:c902:: with SMTP id o2-v6mr4120300pgg.118.1533764562905; Wed, 08 Aug 2018 14:42:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533764562; cv=none; d=google.com; s=arc-20160816; b=czUXkH/yK53xlsmMdutIDdlpK8oB5Nm3XtSsvN2j76DexDBndH/7p9g1KvCt170xuT /6t3OWo0n6sjkInxwr9jn3buuO8OjbGUlXWPLh3OLEDzUHrKtaqjP0NNBgwyZAz9oMIE JQ7huHCorNmV69TZRg04IPBJdLmwoy1esorNx7DBnURATk0HkN4xGZOztLlpg7LqLuop dvrtZsgX2XyoGHv0aG62MzcpvLP01p4nXs9rgiRCxGpIJNVojc8DKc9VhaFIAMEJi7j1 ZPr0mh5RyB9kk2jxTfFr9R+PoTkv1ABFv4l0lBqNrY7fCE/plLt+h8BCkhwMRMm5fVHZ TwEA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=0shRxbx7l+I3iO4Xj6f7GCOaX/R0zYtUnsVawuMowCE=; b=ygM4MNXYXW7vZVn4Hd90rc4b5jrRB670Z4xb+345xPy9jc2yvbKGxax5iK/dZcwG2W KhsJMBdz46hSo+Za+1AVSgU1XvXebxN3CqdR4HlyBFyn6I8YQMhe9xp/tKqm2fBBL7nw I9It4ZxW315VFGvVE7srOGdmVh73VD9aKWT3Vo6imj5n7fhrhdchOfppZT51yve8MZJq KTq4cxfhWKz4VLRhzirq8IzURbrfMdmqFj5fq91hXgaq8/bOnM+krs3+VJalpqhAq8S8 PwPD/0d6SZ+Ky7H353UlJG5XHA2jaxqmMrtw2L2H6yjzK7j89t2E/176eMvLqu6Q3Ihw 5VgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=AkxI1X+n; 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 i3-v6si3967790pli.56.2018.08.08.14.42.27; Wed, 08 Aug 2018 14:42:42 -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=AkxI1X+n; 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 S1730361AbeHIADD (ORCPT + 99 others); Wed, 8 Aug 2018 20:03:03 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:35304 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727706AbeHIADD (ORCPT ); Wed, 8 Aug 2018 20:03:03 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id w78LfQav016131; Wed, 8 Aug 2018 16:41:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1533764486; bh=0shRxbx7l+I3iO4Xj6f7GCOaX/R0zYtUnsVawuMowCE=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=AkxI1X+n7cUmL9nZonD1xyJ8lSxqUtB5MlsNLkY1pDIsSN1uQ0YGsHiRos5cq8gPL 702za863TfnUUVKRUPi7aDCOFbo+JqsiMPfK5tRhYAkPFZ/1L39Xn5xD2fXrzHR3e9 lyVk1O/lJHEuMOZ0zW9m3jwbAC/cp3YlU/CAR9tk= Received: from DLEE114.ent.ti.com (dlee114.ent.ti.com [157.170.170.25]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id w78LfQjH029254; Wed, 8 Aug 2018 16:41:26 -0500 Received: from DLEE106.ent.ti.com (157.170.170.36) by DLEE114.ent.ti.com (157.170.170.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 8 Aug 2018 16:41:26 -0500 Received: from dlep33.itg.ti.com (157.170.170.75) by DLEE106.ent.ti.com (157.170.170.36) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1466.3 via Frontend Transport; Wed, 8 Aug 2018 16:41:25 -0500 Received: from [172.22.156.167] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep33.itg.ti.com (8.14.3/8.13.8) with ESMTP id w78LfP6K006393; Wed, 8 Aug 2018 16:41:25 -0500 Subject: Re: [PATCH v2 1/2] dt: bindings: lm3697: Add bindings for lm3697 driver To: Pavel Machek CC: , , , , References: <20180807160442.8937-1-dmurphy@ti.com> <20180808195903.GB20912@amd> <20180808210215.GA15831@amd> <20180808210926.GC15831@amd> From: Dan Murphy Message-ID: Date: Wed, 8 Aug 2018 16:41:16 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180808210926.GC15831@amd> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit 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 On 08/08/2018 04:09 PM, Pavel Machek wrote: > On Wed 2018-08-08 16:04:43, Dan Murphy wrote: >> On 08/08/2018 04:02 PM, Pavel Machek wrote: >>> Hi! >>> >>>>>> + - #size-cells : 0 >>>>>> + - control-bank-cfg - : Indicates which sink is connected to which control bank >>>>>> + 0 - All HVLED outputs are controlled by bank A >>>>>> + 1 - HVLED1 is controlled bank B, HVLED2/3 are controlled by bank A >>>>>> + 2 - HVLED2 is controlled bank B, HVLED1/3 are controlled by bank A >>>>>> + 3 - HVLED1/2 are controlled by bank B, HVLED3 is controlled by bank A >>>>>> + 4 - HVLED3 is controlled by bank B, HVLED1/2 are controlled by bank A >>>>>> + 5 - HVLED1/3 is controlled by bank B, HVLED2 is controlled by bank A >>>>>> + 6 - (default) HVLED1 is controlled by bank A, HVLED2/3 are controlled by bank B >>>>>> + 7 - All HVLED outputs are controlled by bank B >>>>> >>>>> This is quite long way to describe a bitmask, no? Could we make >>>>> it so that control-bank-cfg is not needed? >>>> >>>> The problem we have here is there is a potential to control >>>> 3 different LED string but only 2 sinks. So control bank A can control 2 LED strings and control >>>> bank b can control 1 LED string. >>>> >>> >>> Can we forget about the LED strings, and just expose the sinks as >>> Linux LED devices? >> >> 2 sinks 3 LED strings. How do you know which LED string is which and what bank it belongs >> to when setting the brightness. Each Bank has a separate register for brightness control. > > Yes, and LED strings are statically assigned to banks, right? > > So why not simply forget about LED strings for sake of hw > abstractions, and work just with banks? How would you set the control bank register for the correct LED string configuration? Dan > Pavel > -- ------------------ Dan Murphy