Re: [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

On Wed, 2011-02-16 at 09:42 -0600, Daniel Morsing wrote:
> On Wed, 2011-02-16 at 16:36 +0200, Tomi Valkeinen wrote:

> > And I found:
> > 
> > http://www.timll.com/chinese/download/files/CHILIN_TECHNOLOGY.pdf
> > 
> > It looks like 24bpp display.
> > 
> 
> Ok I looked through the datasheet and it looks to me that i got
> the .config field right. Only thing that's vague from that sheet is
> which pixel clock edge the v-sync and h-sync are driven low and the
> color distortion is still there with either option.
> 
> > What kind of color distortion do you see? Perhaps the problem is
> > somewhere else, like wrong horizontal sync, vertical sync or pixel clock
> > signal setting in .config field. This info should be in the panel
> > datasheet, but it usually takes some deciphering to understand it =).
> > 
> >  Tomi
> > 
> 
> I'm seeing a light cyan tint to everything when running at 24bpp. Using
> 16 datalines causes a heavy blue tint.

But with 24 datalines and 16 bpp it works? Sounds strange =). 

One thing to check are the pinmuxings (or pad configuration, as it's
called in omap3 trm).

Are you using 2.6.37 or newer kernel?

Is this also happening with other devkit8000 devices, so it's not just a
broken device?

Have you tried with an image with full red, green and blue areas, to see
if only certain colors are affected? 

And the last option is of course get a scope and see what's going on in
the datalines.

 Tomi