linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Query abut 2410 LCD configuration
Date: Wed, 24 Nov 2010 00:34:07 +0000	[thread overview]
Message-ID: <4CEC5D7F.2040503@fluff.org> (raw)
In-Reply-To: <tencent_2B5575C569651C571622EABD@qq.com>

On 08/03/10 14:24, ??? wrote:
> Hi all:)
> 
>       In arch/arm/mach-s3c2410/include/mach/fb.h, struct s3c2410fb_display defines lcd configurations, 
>       Can figure out where does these values following pixclock come from?
> 
> 
> /* LCD description */
> struct s3c2410fb_display {
> 	/* LCD type */
> 	unsigned type;
> 
> 	/* Screen size */
> 	unsigned short width;
> 	unsigned short height;
> 
> 	/* Screen info */
> 	unsigned short xres;
> 	unsigned short yres;
> 	unsigned short bpp;
> 
> 	unsigned pixclock;		/* pixclock in picoseconds */
> 	unsigned short left_margin;  /* value in pixels (TFT) or HCLKs (STN) */
> 	unsigned short right_margin; /* value in pixels (TFT) or HCLKs (STN) */
> 	unsigned short hsync_len;    /* value in pixels (TFT) or HCLKs (STN) */
> 	unsigned short upper_margin;	/* value in lines (TFT) or 0 (STN) */
> 	unsigned short lower_margin;	/* value in lines (TFT) or 0 (STN) */
> 	unsigned short vsync_len;	/* value in lines (TFT) or 0 (STN) 


these values are generally found from the panel's data sheet, detailing
the size of the borders and the length of the sync pulses. These relate
to the standard framebuffer parameters

  parent reply	other threads:[~2010-11-24  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 14:24 Query abut 2410 LCD configuration 胡杨树
2010-03-08 14:32 ` gianluca
2010-11-24  0:34 ` Ben Dooks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-09  0:58 胡杨树
2010-03-12 10:38 ` gianluca

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=4CEC5D7F.2040503@fluff.org \
    --to=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.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).