Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3975944imu; Mon, 7 Jan 2019 13:02:22 -0800 (PST) X-Google-Smtp-Source: ALg8bN6dKkaF4AwSTzGjATCHOf4hjjFm3BstcqOmrg9TfOzWZfeghADihFXD/1Czzp+JKZ6ST/pX X-Received: by 2002:a63:5402:: with SMTP id i2mr11907858pgb.79.1546894942088; Mon, 07 Jan 2019 13:02:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546894942; cv=none; d=google.com; s=arc-20160816; b=EF8S4GoalmTp4xW243s2sLXij1hGxtTM8rFcWcoPN5JvO7LqevZTyZ+9MsL8rjFizM RUgoOB/Tw309T5J45BLv4YzuaIXyUq/Dp65GubLAAqyA3Ayz+qhvsMb6bSF48mwr52z1 HA07knUxNg2vFMwZngZTCW41kxp6HNiRq/J937RGJg93Ot4enlzQXoG1aFmZb0v85WZ7 n6CrinGmi3zXdCBfmyVbfa8LlyeHb8C0x8W+D4qwSTKPevY0irprSfQpeL+TLd9yp1v0 umBAD3Jytiid44MEvfcrZXZ5z08ISW2xfxi5qv9Vlix1ug4ToGyar7oyhJoK7LPuUdoc OCHQ== 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=/jsHHgC2bR0grLfR1pBUFa6w/aCgG1RF9xY9JORnB/o=; b=pccYahYJ2sFOm5nhudcNkGQYWlsKfaL9Iw9pyiWbeU3hBbZhf9AM0UNAOobPaomS26 dcr317BU1546Y4kRQoL4opxSsAZjMZbdCJMfDQy3z7B1u++Fcr410XNwOJoc+V/ZL12L 1J0eXg96D2gYIg/iXK1L0+A7thPFTe3mL4gKs11V8f+4/LwMr9WbLIajWa0dTk1n88XT z75uLpFX44krp7pCCz0jgwKt/if0lhy2f7PpNxmk1+/DVmtDBbVJOlndtGt4HanyipCT pOVEa7h0LTvt+10kidqtwiX0XzAL0A+G6XxAKSAp5eZPvEOuJ8mBkq182z0s4aoJFrsh iiTw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=oRj+iX6k; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 4si7508742plc.320.2019.01.07.13.02.06; Mon, 07 Jan 2019 13:02:22 -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=@gmail.com header.s=20161025 header.b=oRj+iX6k; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727074AbfAGU7u (ORCPT + 99 others); Mon, 7 Jan 2019 15:59:50 -0500 Received: from mail-lj1-f196.google.com ([209.85.208.196]:38291 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726767AbfAGU7u (ORCPT ); Mon, 7 Jan 2019 15:59:50 -0500 Received: by mail-lj1-f196.google.com with SMTP id c19-v6so1561453lja.5; Mon, 07 Jan 2019 12:59:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=/jsHHgC2bR0grLfR1pBUFa6w/aCgG1RF9xY9JORnB/o=; b=oRj+iX6kQS4wT7s9SvDzdLYOZ/976w2NecJLkDiDtEC/ylBypSDsmK6KRr9lWn1MYO F8KPARnp2WzfHrMZn7Xyj5T6vtG2GJe9ytW5j+7JMX9tNk0soOvygTLT8Zg3GwX0VmHg sZd2CgqEEqXAGeesGi/wEU6vKGyTL+borXv7x8h/R/t3es81/eOL0Bu4kggfZ+REW5Ht maUDAqcApxlwp0mFhaL6vlm7jtfJ8AhJckg8huXQAypUNuyIdrIMGO0dmDIMLOmUmGqC 46Ps3A0HaMf80X+x9QDD3gFiyoO0FhYG9s1WaQJ2yz7Sh6YytUVxeqcm0JvTx56LodQE uYhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/jsHHgC2bR0grLfR1pBUFa6w/aCgG1RF9xY9JORnB/o=; b=uKLhAeyuYVy8/nie9z8PO0Fwnz/D9eFCmXKXgsSfKDTTKyKJkBa0KVlSYMS8fD3csk lQI8MSWaC9ubVr7p4Gft0xdXzszDQgfKIQPxYzLnBFRJ4zVD6sQQlGvxCiiguQFJZyEK vsrUvnqsUkIY+X4wPrWvLfrvqRNs4jaobPu6uJgVhmtrV884rnyd0Stt8sJ+FiMXsrto 2DWQ71knf74h4/DVXuhOKNRxKjrWSQcXXejoe9Di58RjmP12jmRl6H1Ds6XhO87wVUnW LKZql489wcWc9IJE57uFmJIbLY35WWY8Up8Q+H3njSsPTkCjbsVtK3lwKrZg1sZCUKdC qkzw== X-Gm-Message-State: AJcUukcvGW7I2HI4NX9xMxmRb1bCsR3mq1EWo5332Fq/Ky+cXQcxoKZt xYsnM8nqEOQfSNsy6u8Krbu6aOwr X-Received: by 2002:a2e:9715:: with SMTP id r21-v6mr34866590lji.30.1546894786253; Mon, 07 Jan 2019 12:59:46 -0800 (PST) Received: from [192.168.1.18] (dnq218.neoplus.adsl.tpnet.pl. [83.24.98.218]) by smtp.gmail.com with ESMTPSA id 11-v6sm13771857ljv.1.2019.01.07.12.59.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Jan 2019 12:59:45 -0800 (PST) Subject: Re: Generic RGB LED support was Re: [PATCH 2/2] leds: lp5024: Add the LP5024/18 RGB LED driver To: Dan Murphy , Pavel Machek Cc: =?UTF-8?B?VmVzYSBKw6TDpHNrZWzDpGluZW4=?= , robh+dt@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org References: <986b5105-2fdb-bd25-7c8a-ca8fd1ade821@gmail.com> <7f205102-e854-f1cb-cc03-1307d1cddc87@gmail.com> <20190104201256.GA2931@amd> <20190104220726.GA12395@amd> <4cf79414-578e-eea7-4f46-fc8789206988@gmail.com> <20190105123146.GA16354@amd> <8044cdd9-b9b3-fddd-6106-184b906859e2@gmail.com> <20190105221254.GA22322@amd> <70366f2a-aafd-174f-73ec-a8117133b7af@gmail.com> From: Jacek Anaszewski Message-ID: <2c3425b0-70af-1f38-35ee-0af857bf0539@gmail.com> Date: Mon, 7 Jan 2019 21:59:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dan, On 1/7/19 8:36 PM, Dan Murphy wrote: > Jacek > > On 1/7/19 1:13 PM, Jacek Anaszewski wrote: >> On 1/6/19 4:52 PM, Jacek Anaszewski wrote: >>> Hi Pavel, >>> >>> On 1/5/19 11:12 PM, Pavel Machek wrote: >>>> Hi! >>>> >>>>>> Grab yourself an RGB LED and play with it; you'll see what the >>>>>> problems are. It is hard to explain colors over email... >>>>> >>>>> Video [0] gives some overview of lp5024 capabilities. >>>>> >>>>> I don't see any problems in exposing separate red,green,blue >>>>> files and brightness for the devices with hardware support for >>>>> that. >>>> >>>> Well, that's what we do today, as three separate LEDs, right? >>> >>> No. It doesn't allow for setting color intensity by having >>> the color fixed beforehand. Below is relevant excerpt from >>> the lp5024 documentation. This is not something that can be >>> mapped to RGB color space, but rather to HSV/HSL, with the >>> reservation that the hardware implementation uses PWM >>> for setting color intensity. >>> >>> >>> 8.3.1.2 Independent Intensity Control Per RGB LED Module >>> >>> When color is fixed, the independent intensity-control is used to >>> achieve accurate and flexible dimming control for every RGB LED module. >>> >>> 8.3.1.2.1 Intensity-Control Register Configuration >>> >>> Every three consecutive output channels are assigned to their respective >>> intensity-control register (LEDx_BRIGHTNESS). For example, OUT0, OUT1, >>> and OUT2 are assigned to LED0_BRIGHTNESS, so it is recommended to >>> connect the RGB LEDs in the sequence as shown in Table 1. The LP50xx >>> device allows 256-step intensity control for each RGB LED module, which >>> helps achieve a smooth dimming effect. >>> >>> >>>> I don't have problem with that, either; other drivers already do >>>> that. He's free to use existing same interface. >>>> >>>> But that is insufficient, as it does not allow simple stuff, such as >>>> turning led "white". >>>> >>>> So... perhaps we should agree on requirements, first, and then we can >>>> discuss solutions? >>>> >>>> Requirements for RGB LED interface: >>>> >>>> 1) Userspace should be able to set the white color >>>> >>>> 2) Userspace should be able to arbitrary color from well known list >>>> and it should approximately match what would CRT, LCD or OLED monitor display >>> >>> The difference is that monitor display driver is pre-calibrated >>> for given display by the manufacturer. With the LED controllers the >>> manufacturer has no control over what LEDs will be connected to the >>> iouts. Therefore it should be not surprising that colors produced >>> by custom LEDs are not as user would expect when comparing to >>> the RGB color displayed on the monitor display. >>> >>> TI provides "Various LED Ring Lighting Patterns Reference Design" [0] >>> that show how to produce various patterns with use of the reference >>> board with LED ring built using sixteen 19-337/R6GHBHC-A01/2T LEDs [1]. >>> >>> Document [0] mentions also specific "Design considerations" in the >>> chapter 2.2: >>> >>> >>> Several considerations are taken into account for this particular design: >>> ? LED map (ring) for meeting the requirement of popular human-machine interaction style. >>> ? LED size, numbers and the diffuse design for meeting lighting pattern uniformity. >>> ? Analog dimming in the difference ambient light lux without losing dimming resolution in lighting pattern. >>> >>> These considerations apply to most human-machine interaction end equipment with day and night vision >>> designs in some way, but the designer must decide the particular considerations to take into account for a >>> specific design. >>> >>> >>> This renders your requirement 2) infeasible with use of custom LEDs >>> any fixed algorithm, since the final effect will always heavily depend >> >> Typo here: s/any fixed/and fixed/ >> >>> on the LED circuit design. >>> >>>> >>>> ???? 2a) LEDs probably slightly change color as they age. That's out of >>>> ???? scope, unless the variation is much greater than on monitors. >>>> >>>> ???? 2b) Manufacturing differences cause small color variation. Again, >>>> ???? that's out of scope, unless the variation is much greater than on >>>> ???? monitors. >>>> >>>> Nice to have features: >>>> >>>> 3) Full range of available colors/intensities should be available to >>>> userspace >>>> >>>> 4) Interface should work well with existing triggers >>>> >>>> 5) It would be nice if userland knew how many lumens are produced at >>>> each wavelength for each setting (again, minus aging and manufacturing >>>> variations). >>>> >>>> 6) Complexity of math in kernel should be low, and preferably it >>>> should be integer or fixed point >>>> >>>> Problems: >>>> >>>> a) RGB LEDs are usually not balanced. Setting 100% PWM on >>>> red/green/blue channels will result in nothing close to white >>>> light. In fact, to get white light on N900, blue and green channel's >>>> PWM needs to be set pretty low, as in 5%. >>>> >>>> b) LED class does not define any relation between "brightness" in >>>> sysfs and ammount of light in lumens. Some drivers use close to linear >>>> relation, some use exponential relation. Human eyes percieve logarithm >>>> of lumens. RGB color model uses even more complex function. >>>> >>>> c) Except for white LEDs, LEDs are basically sources of single >>>> wavelength of light, while CRTs and LCDs produce broader >>>> spectrums. >>>> >>>> d) RG, RGBW and probably other LED combinations exist. >>>> >>>> e) Not all "red" LEDs will produce same wavelength. Similar >>>> differences will exist for other colors. >>>> >>>> f) We have existing RGB LEDs represented as three separate >>>> monochromatic LEDs in sysfs. >>> >>> One general question: do you have any solutions in store? >>> >>> [0] http://www.ti.com/lit/ug/tiduee6/tiduee6.pdf >>> [1] http://www.everlight.com/file/ProductFile/19-337-R6GHBHC-A01-2T.pdf >>> >> > > I just wanted to point out that there are 4 total devices right now that use the same mapping > > LP5018, LP5024, LP5030 and the LP5036. > > I can implement what ever we would like to I just need to know what to design against. As you can see from the discussion in this thread it may take some time to work out the interface satisfying everyone. I made some design proposal, but Pavel had no warm word for it. It would be easier if we had more opinions. How do you feel about using brightness file for setting LEDn_BRIGHTNESS? Does increasing LEDn_BRIGHTNESS value (i.e. color intensity) feel like increasing color lightness (i.e. the pattern presented in the video [0] starting from 1:22)? > But keep in mind I still need to invest my time in the other TI-lmu patches on my list to complete. Do what you deem most suitable for you. We are here only to help merging the patches, but keeping in mind that kernel interface once introduced must be preserved forever. Therefore we need to do our best to make the best possible design decisions. [0] https://www.youtube.com/watch?v=qdt-alh8i6E -- Best regards, Jacek Anaszewski