Pavel On 3/2/19 5:07 PM, Pavel Machek wrote: > Hi! > >> I just want to follow up here and let you know that I have not abandoned >> this. >> I am trying to rework and fix up the ti lmu binding as asked by Pavel. Its >> proving >> to be a bit of a challenge based on looking forward to what will be the >> implementation. >> >> I also did go offline and speak with Tony. I have a Droid 4 so I can test >> all of this on >> production hardware as well. >> >> Updated patchset will take some time to get out. > > Is there any progress here? > > This is needed for display on Droid 4, so it is somehow > important... and Milo Kim's patches are pretty reasonable. > > I still believe best way forward is to merge them, and let you submit > any improvements on top of them... >
I had looked at this a while back. And I will pick this up again as it seems that the multi color framework will take longer than expected. For the Droid 4 it uses the lm3552 backlight driver, at least that is what is in the DT. There is a lm3530 backlight driver that is already available and could be upgraded to DT support and have the lm3552 added to it but the issues are the 3532 has 3 outputs and the 3530 has 1 and the register map is a bit different. There are register differences between the two devices but the driver already has ramp support, PWM support (exponential/linear), ALS support and manual support already available along with user space configuration. I was working on creating a new lm3532 driver based off the lm3530 driver or adapting the 3530 to include the 3532 and making the driver generic to this family. Dan > Best regards, > Pavel > -- ------------------ Dan Murphy
