linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Ian Campbell <icampbell@arcom.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] PXA255 LCD Driver
Date: Sat, 20 Mar 2004 09:06:07 +0000	[thread overview]
Message-ID: <20040320090607.A27266@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0403192352580.14905-100000@phoenix.infradead.org>; from jsimmons@infradead.org on Sat, Mar 20, 2004 at 12:01:03AM +0000

On Sat, Mar 20, 2004 at 12:01:03AM +0000, James Simmons wrote:
> We can have it so that we can pass in a monitor string that can be used to 
> select the proper LCD panel in the database. How does that sound?

That's still a little problematical because some hardware people put
a CPLD between the LCD controller and the LCD panel itself which
may change the characteristics.

It's fairly common to have one LCD controller appear in many different
devices (because its part of the CPU) and have the same display, yet
need different timing.

For example, see sa1100fb.c:

static struct sa1100fb_mach_info lq039q2ds54_info __initdata = {
        .pixclock       = 171521,       .bpp            = 16,
        .xres           = 320,          .yres           = 240,

        .hsync_len      = 5,            .vsync_len      = 1,
        .left_margin    = 61,           .upper_margin   = 3,
        .right_margin   = 9,            .lower_margin   = 0,

        .sync           = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,

        .lccr0          = LCCR0_Color | LCCR0_Sngl | LCCR0_Act,
        .lccr3          = LCCR3_OutEnH | LCCR3_PixRsEdg | LCCR3_ACBsDiv(2),
};

static struct sa1100fb_mach_info h3600_info __initdata = {
        .pixclock       = 174757,       .bpp            = 16,
        .xres           = 320,          .yres           = 240,

        .hsync_len      = 3,            .vsync_len      = 3,
        .left_margin    = 12,           .upper_margin   = 10,
        .right_margin   = 17,           .lower_margin   = 1,

        .cmap_static    = 1,

        .lccr0          = LCCR0_Color | LCCR0_Sngl | LCCR0_Act,
        .lccr3          = LCCR3_OutEnH | LCCR3_PixRsEdg | LCCR3_ACBsDiv(2),
};

Both of these are the same LCD panel (type LQ039Q2DS54) yet there are
two different sets of timing information, including the polarity of
the line and field clocks (which are equivalent to hsync and vsync.)

Also note that such panels are generally fixed resolution, though there
are a few rare exceptions where changing the colour depth is permitted.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-20  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1079518182.13373.27.camel@icampbell-debian>
2004-03-17 10:39 ` [PATCH] PXA255 LCD Driver Geert Uytterhoeven
2004-03-17 11:07   ` Ian Campbell
2004-03-17 11:15     ` Geert Uytterhoeven
2004-03-17 12:06       ` Ian Campbell
2004-03-17 19:03         ` James Simmons
2004-03-18 11:05           ` Ian Campbell
2004-03-20  0:01             ` James Simmons
2004-03-20  9:06               ` Russell King [this message]
2004-03-20 11:24                 ` Ian Campbell
2004-03-20 11:24               ` Ian Campbell
2004-03-18 20:36           ` Russell King
2004-03-19 23:52             ` James Simmons
2004-03-25 17:13               ` Ian Campbell
2004-03-17 17:18 ` James Simmons

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=20040320090607.A27266@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=icampbell@arcom.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).