Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10966571imu; Mon, 31 Dec 2018 10:05:52 -0800 (PST) X-Google-Smtp-Source: ALg8bN65jOBrP49H0HbCmN0zPyEHmH4HyMkNI0HW5Jhn0ZpO6Nj/MGda4S7mgODmUZsy/l5R0w3G X-Received: by 2002:a17:902:3283:: with SMTP id z3mr38496162plb.76.1546279552502; Mon, 31 Dec 2018 10:05:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546279552; cv=none; d=google.com; s=arc-20160816; b=SvIRsbWUb+HsE7DzGLOxjMJBjM5ND1o0VzijgQPSgYsBeaQL4fzy+OJ6DXql2Da5PJ iFJ2z6s29OR3FvW1UMwP12/tnbYDkpX6nN+URCi2g5JAa4BD13n2J6NnuwoXFfjZgDVW CyBVw+jJF6hAnfJzPwmL9hCGDmcWFsg/g7Pg6rEazFjy8F04PdTS+ALfA+hjytPZ9WI0 XbrIz4HjTKw4i8ljlF0ukk15H27wMjsZRkCTEhOkWjWoF5CXWmAhpHPEvSLid5XMf0DX dPW/DbZOCaWotSOJVxGJBMiBfW2heLR3+6ryLlKO6cvpEuQ1fXIGuM9ycREAXnqcfLpu TrFA== 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=opV65RXXDmfBErUf74s/reYSPpfVS5V3bSTm3np5Qis=; b=eBPouqf0MzwRI/UJy+LYTwaSyxuPWYICJNasYxrFp9zfDaYKGSZwvowMDEPT7AQTWw i3yud6imnjbani/5sZl4Eaffl8De5fPzJ6iiGHvIwSWNJGsyp1QrVRlc54TSMndbvzRp e09GnPw1Oo6a9xckV7mdWDjcDy5eyQFr8nkuJ7OHkQTCG3IptmYo91h83CA/UsBvTpxn RP4OnCbwUA+fRQjU79CBOU3NXKlx/IpSW0oVtPdRrlGbYyrPtRvqQdQJFuShpYJGbHdj MNe4mmMVybKPuVxnGony+RakCHQrcukCTaF8dosnbSdquDDYhSP5ie/Y9qSZuAW1iSrD fSZw== 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 f61si47025444plb.51.2018.12.31.10.05.37; Mon, 31 Dec 2018 10:05:52 -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 S1727507AbeLaQ2c (ORCPT + 99 others); Mon, 31 Dec 2018 11:28:32 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:59233 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727367AbeLaQ2c (ORCPT ); Mon, 31 Dec 2018 11:28:32 -0500 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 5CDDD80805; Mon, 31 Dec 2018 17:28:24 +0100 (CET) Date: Mon, 31 Dec 2018 17:28:28 +0100 From: Pavel Machek To: Jacek Anaszewski Cc: Dan Murphy , robh+dt@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org Subject: Re: [PATCH 2/2] leds: lp5024: Add the LP5024/18 RGB LED driver Message-ID: <20181231162828.GA8846@amd> References: <54f28115-0a7d-8e9c-3bec-6e91fb3981ec@gmail.com> <71d3ac12-5beb-0a26-71e1-5eae798e7b9f@gmail.com> <2bca210b-76ad-d5a9-906c-4151695050c3@gmail.com> <45ce01f0-af6e-1cc6-5126-fb557c7d2a82@ti.com> <20181229190726.GA29851@amd> <4b5a89ed-0c0b-3103-ca57-a0f97aa5ace9@gmail.com> <20181230173505.GA19593@amd> <7763a3ae-343c-0fbe-da88-afce8459e4c2@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <7763a3ae-343c-0fbe-da88-afce8459e4c2@gmail.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 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >>>>There is still HSV approach [0] in store. One problem with proposed > >>>>implementation is fixed algorithm of RGB <-> HSV color space conversi= on. > >>>>Maybe allowing for some board specific adjustments in DT would add > >>>>more flexibility. > >>>> > >>>>[0] https://lkml.org/lkml/2017/8/31/255 > >>> > >>>Yes we could do HSV. Problem is that that we do not really have RGB > >>>available. We do have integers for red, green and blue, but they do > >>>not correspond to RGB colorspace. > >> > >>OK, so conversion from HSV to RGB would only increase the aberration. > >>So, let's stick to RGB - we've got to have some stable ground and this > >>is something that the hardware at least pretends to be compliant > >>with. > > > >I'm not saying that we should stick to RGB. I'm just saying that > >problem is complex. > > > >And no, hardware does not even pretend to be compliant with RGB color > >model ( https://en.wikipedia.org/wiki/RGB_color_model ). In > >particular, in RGB there is non-linear brightness curve. >=20 > Quotation from the wiki page you referred to: >=20 > "RGB is a device-dependent color model: different devices detect or > reproduce a given RGB value differently, since the color elements (such > as phosphors or dyes) and their response to the individual R, G, and B > levels vary from manufacturer to manufacturer, or even in the same > device over time. Thus an RGB value does not define the same color > across devices without some kind of color management" >=20 > This claim alone leaves much room for the manufacturers to pretend that > their devices are compliant with RGB model. Much room, but everyone agrees that R=3DG=3DB=3D255 should be some kind of white, and what other colors "approximately" mean.=20 I have two monitors, and no, colors don't match. Do you have access to RGB led? Try to compare two monitors, and then RGB led with monitor. RGB led will be _way_ off. This chart makes sense: https://www.rapidtables.com/web/color/RGB_Color.html Try it on your LED device... > >I believe problem to start with is the "white" problem. Setting > >R=3DG=3DB=3D255 will _not_ result in anything close to white light on > >hardware I have. >=20 > RGBW LED controllers solve this problem. For the devices without > white/amber we cannot do more than the hardware allows for. But the hardware can do some kind of white. It is just that R=3DG=3DB=3D255 will result in green-ish-blue and something like R=3D255, G=3D50, B=3D10 is neccessary to get approximation of white. IMO good start would be to specify what kind of intensities are neccessary to approximate white. And then try converting from RGB to led intensities, and see if it somehow works. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlwqQ6wACgkQMOfwapXb+vJNZwCghwg2SD5PmRNKA//menJsT9pL 5WkAn21UrJAaED3VNBEzYGp+E3OIfzEq =+Bi5 -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--