Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp90074imu; Wed, 19 Dec 2018 14:13:20 -0800 (PST) X-Google-Smtp-Source: AFSGD/V6V8dC5w8zsN4IxwBj4Pz9ANH08FXLk94DUxku/xV/6fAVQANQje+QKqmCgQH8rQHm/DKD X-Received: by 2002:a62:a1a:: with SMTP id s26mr22147024pfi.31.1545257600805; Wed, 19 Dec 2018 14:13:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545257600; cv=none; d=google.com; s=arc-20160816; b=GyS9tQMZol28LbIE4KwQx9e9jOzxufE5WkWAMHmV7EYKfZGiYi/jpQRZumxL0jZJ2H 8ybRWj2Qyc4fLHEc04J6xoVhTnMYpR218SfahxN81jR4VQdXPXkYitn45geSKC+oY5Ln URfrpgfvT4ZAiBERpjvaz+6tS8LWr8o8LNRI+BwJzhlqr8F7xJHOaDT6LhPqPpCjqWom t3W2frOqbNLikhuITfebd4HmKOk/wXnkvr89IGm43OQ+YfCx4zsCJG+gyQzHOJA5GXox xYzFeaKqplwkixzgzy2Eh1CDY/wE2m5WMAlFeR+BSJyvNeWfo+7nAxHMkTvswjcaHl/a DMNQ== 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; bh=8n7mFMZsU9E5bR46OHHKnWJuEq1e4yDI7ELGWwTKjmw=; b=fLyMtvzPHvqTsZxDiaPHUqKbW9YYNse6BK+KagRcdgluCkHre+f1ZnH+Kze+RdyF/A xKblTxNEkA9ruqrDzMuKmmipgu2iTtZBSzt9sDd/VxTcUyirkBT3CRa7NiGw7V8wdAh8 FmFUH/zXyaqPjkKp5RRDplKHoNiBtdYOxkT0G3dA7mOUd0CtD98obVD2vLYJhvoY1hSd a7Pm/ltQhSmjU83nd2ozya7MNYvIs4OEBtI+8OIOQgzUjykg6JBwcU9AwAXKxEfukBZf s8oa6UBpoUuV64DC/7StnyoJyncRAx9QVGUM+yjkkTM/FEaggqXvLRjfw0ggmg/7ozMo pH5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=QSDLlDgZ; 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 y6si17241039pfi.228.2018.12.19.14.13.04; Wed, 19 Dec 2018 14:13:20 -0800 (PST) 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=QSDLlDgZ; 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 S1730315AbeLSUlL (ORCPT + 99 others); Wed, 19 Dec 2018 15:41:11 -0500 Received: from fllv0015.ext.ti.com ([198.47.19.141]:37020 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729585AbeLSUlK (ORCPT ); Wed, 19 Dec 2018 15:41:10 -0500 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id wBJKf5OO008999; Wed, 19 Dec 2018 14:41:05 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1545252065; bh=8n7mFMZsU9E5bR46OHHKnWJuEq1e4yDI7ELGWwTKjmw=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=QSDLlDgZkHZvnjipEHmKmzq4Sm1O38e/7Yrkniw4u/5mQVdCG3ZX0pLCMv7XWtmI4 gyMbXz4X8Prm94IeaMgIRXRPHRxucW6+RD8d0yZJPJ8HtLKS/KreR5wPBHiwTxyUL4 kOa2E/qKyfwXWbdMHDuSBurFJYr0bJ69xQ2iUPX8= Received: from DFLE102.ent.ti.com (dfle102.ent.ti.com [10.64.6.23]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id wBJKf5KT014076 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 19 Dec 2018 14:41:05 -0600 Received: from DFLE109.ent.ti.com (10.64.6.30) by DFLE102.ent.ti.com (10.64.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Wed, 19 Dec 2018 14:41:05 -0600 Received: from dlep32.itg.ti.com (157.170.170.100) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1591.10 via Frontend Transport; Wed, 19 Dec 2018 14:41:05 -0600 Received: from [172.22.106.233] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id wBJKf5xI020574; Wed, 19 Dec 2018 14:41:05 -0600 Subject: Re: [PATCH 2/2] leds: lp5024: Add the LP5024/18 RGB LED driver To: Pavel Machek CC: , , , , References: <20181219162626.12297-1-dmurphy@ti.com> <20181219162626.12297-3-dmurphy@ti.com> <20181219193455.GA21159@amd> <8740cfd6-a6b5-ad27-313b-984a9febf18a@ti.com> <20181219201047.GA23448@amd> From: Dan Murphy Message-ID: Date: Wed, 19 Dec 2018 14:41:04 -0600 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: <20181219201047.GA23448@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 Pavel On 12/19/2018 02:10 PM, Pavel Machek wrote: > On Wed 2018-12-19 13:41:18, Dan Murphy wrote: >> Pavel >> >> Thanks for the review. >> >> On 12/19/2018 01:34 PM, Pavel Machek wrote: >>> Hi! >>> >>>> +static DEVICE_ATTR_WO(ctrl_bank_a_mix); >>>> +static DEVICE_ATTR_WO(ctrl_bank_b_mix); >>>> +static DEVICE_ATTR_WO(ctrl_bank_c_mix); >>>> + >>>> +static struct attribute *lp5024_ctrl_bank_attrs[] = { >>>> + &dev_attr_ctrl_bank_a_mix.attr, >>>> + &dev_attr_ctrl_bank_b_mix.attr, >>>> + &dev_attr_ctrl_bank_c_mix.attr, >>>> + NULL >>>> +}; >>>> +ATTRIBUTE_GROUPS(lp5024_ctrl_bank); >>> >>> ... >>>> + >>>> +static DEVICE_ATTR_WO(led1_mix); >>>> +static DEVICE_ATTR_WO(led2_mix); >>>> +static DEVICE_ATTR_WO(led3_mix); >>>> + >>>> +static struct attribute *lp5024_led_independent_attrs[] = { >>>> + &dev_attr_led1_mix.attr, >>>> + &dev_attr_led2_mix.attr, >>>> + &dev_attr_led3_mix.attr, >>>> + NULL >>>> +}; >>>> +ATTRIBUTE_GROUPS(lp5024_led_independent); >>> >>> Ok, so you are adding new sysfs files. Are they _really_ neccessary? >>> We'd like to have uniform interfaces for the leds. >> >> Yes I am adding these for this driver. >> They adjust the individual brightness of each LED connected (what the HW guys called mixing). >> >> The standard brightness sysfs adjusts all 3 LEDs simultaneously so that all 3 LEDs brightness are >> uniform. > > 1 LED, 1 brightness file... that's what we do. Why should this one be different? > Yes I understand this and 1 DT child node per LED out but... This device has a single register to control 3 LEDs brightness as a group and individual brightness registers to control the LEDs independently to mix the LEDs to a specific color. There needs to be a way to control both so that developers can mix and adjust the individual RGB and then control the brightness of the group during run time without touching the "mixing" value. I don't think a user needs nor would want to have 24 different LED nodes with 24 different brightness files. Or with the LP5036 that would have 36 LED nodes. Table 1 in the data sheet shows how the outputs map to the control banks to the LED registers. Dan >> I did not think these belonged in the dt as they should be user space configurable >> >>> >>> If they are neccessary, we need documentation for them. >> >> Sure I have no problem documenting them but where do I do that? >> I am assuming Documentation/leds/leds-lp5024.txt > > Documentation/abi/... > > Pavel > -- ------------------ Dan Murphy