From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH 2/2] leds: lp5024: Add the LP5024/18 RGB LED driver Date: Wed, 19 Dec 2018 23:27:37 +0100 Message-ID: <20181219222737.GB30496@amd> 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> <54f28115-0a7d-8e9c-3bec-6e91fb3981ec@gmail.com> <20181219220326.GA28244@amd> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Dan Murphy Cc: jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org, kernel list List-Id: linux-leds@vger.kernel.org --i0/AhcQY5QxfSsSZ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! [cc list trimmed] > >>> I don't think a user needs nor would want to have 24 different LED no= des 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 ba= nks to the LED registers. > >> > >> Some time ago we had discussion with Vesa J=E4=E4skel=E4inen about pos= sible > >> approaches to RGB LEDs [0]. What seemed to be the most suitable > >> variation of the discussed out-of-tree approach was the "color" proper= ty > >> and array of color triplets defined in Device Tree per each color. > >> > >> Please refer to [0] for the details. > >> > >> [0] https://lkml.org/lkml/2018/11/9/938 > >=20 > > Yes, plus I also have the set of HSV patches somewhere... and they > > work, but I found out that HSV->RGB conversion results in loss of preci= sion. > >=20 > > We may want to do something like that. > >=20 > > But we need to do it once, in a driver core. We obviously don't want > > each driver having different version of RGB support. >=20 > True. But the RGB driver really should not be defining the color palette. >=20 > Maybe a "color capability" reported to user space so that the user space = can make the decision. >=20 > It can report >=20 > For GPIO or constant current situations > static red > static blue > static green=20 >=20 > For adjustable configurations it can report: > variable red > variable blue > variable green >=20 > or even simpler "static" or "dynamic" as a return to report the RGB confi= guration. > The LED driver would just need to set the variable. I'm not sure what static/variable is. I have RGB leds here that can set any channel to 0-255, at runtime. They seem to be quite common at phones. Anyway, if your 36 channels can be set independently, I believe you just want them to export as 36 LEDs. Thanks, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --i0/AhcQY5QxfSsSZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlwaxdkACgkQMOfwapXb+vIV3QCfcYJM8VPdCZQxaX0y9mrvxKRl FQ0AnRIzgL0rg5Yy6TRRBbLLSJSSKWrp =gkmt -----END PGP SIGNATURE----- --i0/AhcQY5QxfSsSZ--