From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Daniel Morsing <daniel.morsing@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Bryan Wu <bryan.wu@canonical.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi
Date: Wed, 16 Feb 2011 14:36:36 +0000 [thread overview]
Message-ID: <1297866996.988.69.camel@deskari> (raw)
In-Reply-To: <1297865193.8777.8.camel@morsing>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1650 bytes --]
On Wed, 2011-02-16 at 08:06 -0600, Daniel Morsing wrote:
> Hi Tomi
>
> On Wed, 2011-02-16 at 15:11 +0200, Tomi Valkeinen wrote:
> > Hi,
> >
> > On Sat, 2011-02-12 at 11:02 -0600, Daniel Morsing wrote:
> > > The panel added is the 4.3 inch display that is sold with the
> > > Devkit8000.
> >
> > Hmm. Devkit8000's panel is connected with 24 datalines, according to the
> > board file. Why do you want to use 16 bpp format for that?
> >
> > Tomi
> >
>
> Running the panel at 24 bpp or specifying 16 datalines causes color
> distortion.
>
> The only way I've been able to run the panel without color distortion,
> is with 24 datalines and 16 bpp.
>
> I'm not well versed in displays, so I might be making a mistake
> somewhere. The BSP for the devkit8000 doesn't include a datasheet for
> the panel, so I can't look into what's causing this weirdness.
I don't think I'll add a feature which doesn't make sense, to fix a
problem we don't understand =).
A datasheet I found mentions
"One 4.3” TFT LCD (With Touch panel, CHI HSIN LR043JC211 LCD
Model)"
And I found:
http://www.timll.com/chinese/download/files/CHILIN_TECHNOLOGY.pdf
It looks like 24bpp display.
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
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-16 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 17:02 [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi panels Daniel Morsing
2011-02-12 17:02 ` [PATCH 1/2] omap: dss2: Add recommended bpp option for " Daniel Morsing
2011-02-12 17:02 ` [PATCH 2/2] omap3: devkit8000: Add and use 4.3 inch display Daniel Morsing
2011-02-16 14:42 ` Thomas Weber
2011-02-18 12:36 ` Thomas Weber
2011-02-18 12:55 ` Daniel Morsing
2011-02-18 13:07 ` Tomi Valkeinen
2011-02-18 16:18 ` Daniel Morsing
2011-02-18 16:43 ` Tomi Valkeinen
2011-02-16 13:11 ` [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi Tomi Valkeinen
2011-02-16 14:06 ` Daniel Morsing
2011-02-16 14:36 ` Tomi Valkeinen [this message]
2011-02-16 15:42 ` Daniel Morsing
2011-02-16 15:58 ` Tomi Valkeinen
2011-02-16 19:22 ` Daniel Morsing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297866996.988.69.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=bryan.wu@canonical.com \
--cc=daniel.morsing@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).