Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1725247imu; Thu, 17 Jan 2019 02:09:36 -0800 (PST) X-Google-Smtp-Source: ALg8bN43TLQvLKlC9SQN4NlwevpygUzcAb/Kh/5kMVZusXAGhObYQPqN3Nv66RTj8KUoZTlwX9mv X-Received: by 2002:a62:81c1:: with SMTP id t184mr14685617pfd.40.1547719776866; Thu, 17 Jan 2019 02:09:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547719776; cv=none; d=google.com; s=arc-20160816; b=LYnOoJRr9BJAcSJ82bAyPO3mWWMEWHhdrXwCqOl9qSeyg9gCg5+GOS/0h7LZ4TSi2e vqfODyYw2aB5Fx3RQP70hLqOpt7kW5leHECGcKY4UbLgwYWjr4X8FT54yBcoVbeBfJ4M fXQCTNRQNCSN9mFO/7Tmc3iX7rpsGFJbqnMiAMX6GlK0AddPxe/BVLFpVtJQC2EbND5W wsO2CsFOV1ebbAEM/oQa6L+RxWP/BercU8gBanDhI0psTz48ZrE9+003Q9y86Om0aMFH xigZo3zDXMo+JZKepvam4T4ya0NgWx/Dz5VkK37b6xj+uqn7DztLLoJ8qDgj8IPWyuCL /dmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Dd5TVIEz3VL1/zahR6gJQ0tUnBKZijKBnEmSXQNGYFw=; b=PJBNukWwfSjeXF+70g0hN2xUXMoIufxDTxYnS55kJ8MlpRnnTX7LXd+LvT65sR5MOj uXEtTnWORuGuzITILAFTp/Qj0jQkyYYfKT5GJuWuiq2+L/vn4fmfdkFOftdf6xZ84DXE 9CumnAyCIkLMbG33kpcoHqW+WkXdyVjIkVBrECegCgxC2Vh6Tok0a9GqQduBvKkOxWVj XlK+eccrDk7KOYROVjMnJ0HAyRarBuSGdRNKykzPbLnvhBsvshoZaSvLUSDHNcniGd9a ZbE1/QltFK4JwNqKs3EFs7qlbX3R67yxikiWJD4TvViY7VoSOp95xD2qsUaFueHE5kov cBcg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a11si1264839pln.78.2019.01.17.02.09.20; Thu, 17 Jan 2019 02:09:36 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727892AbfAQKGz (ORCPT + 99 others); Thu, 17 Jan 2019 05:06:55 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:37628 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725990AbfAQKGy (ORCPT ); Thu, 17 Jan 2019 05:06:54 -0500 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 71D0C807A7; Thu, 17 Jan 2019 11:06:46 +0100 (CET) Date: Thu, 17 Jan 2019 11:06:51 +0100 From: Pavel Machek To: Dan Murphy Cc: Jacek Anaszewski , linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, dachaac@gmail.com, robh+dt@kernel.org Subject: Re: [PATCH v2 2/2] leds: lp50xx: Add the LP50XX family of the RGB LED driver Message-ID: <20190117100651.GB17930@amd> References: <20190114211723.11186-1-dmurphy@ti.com> <20190114211723.11186-2-dmurphy@ti.com> <20190115222223.GA17363@amd> <79394d17-3124-75b2-ccac-dc1046499d14@ti.com> <20190116105537.GA1803@amd> <86299268-3202-814a-134b-04bd2170faab@ti.com> <20190116220401.GA28024@amd> <8c7dde3e-5f3c-80a5-ec57-73ce8e39deef@ti.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <8c7dde3e-5f3c-80a5-ec57-73ce8e39deef@ti.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >>> You know what? First, submit driver with similar functionality to > >>> existing RGB drivers, using same interface existing drivers are > >>> using. When that is accepted, we can talk about extending > >>> kernel<->user interfaces. > >>> > >> > >> I could do that but then there is no way for users to have any other c= olor but "white" with this driver. > >> That defeats the purpose of the device itself. > >=20 > > No, that is not what I meant. > >=20 > > We do have RGB drivers in tree, they just present three separate LEDs > > -- red, green and blue. I ask you to do the same for initial > > submission. > >=20 >=20 > For clarification you are asking me to register a LED class per > output pin? Yes. > As explained before the Master brightness register has absolute control o= ver the output current > to the LED outputs regardless of the color control setting. >=20 Yes, just set master brightness to 255 and you can ignore it. > > You'll still be able to set brightness independently on the > > red/green/blue LEDs... > >=20 >=20 > But which one would control the overall brightness of the cluster? You would not have that control in initial version of the patch. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlxAU7sACgkQMOfwapXb+vLcUwCgk7gzWalf88kSfQTICoLiUKgw xMIAoI7BHm0fNZlXPU3Cqctc5PX+JhlV =x4S1 -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H--