From: Eric Miao <eric.y.miao@gmail.com>
To: Jun Nie <niej0001@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/6] pxa: fix pxa168 lcd controller vsync/hsync timing error
Date: Mon, 9 Nov 2009 11:39:30 +0800 [thread overview]
Message-ID: <f17812d70911081939nf30b893vc8a9b3cf821fc78@mail.gmail.com> (raw)
In-Reply-To: <7c34ac520911041815k6555e209r4039ae9f97c9ebca@mail.gmail.com>
>> Could you please help double check this? My understanding is
>> FB_SYNC_VERT_HIGH_ACT means it's a positive pulse covering all the
>> valid HSYNCs, and a rising edge of VSYNC means a start of the frame.
>>
>> However, CFG_INV_VSYNC is '1' means the opposite.
>>
>
> My understanding is that high active means high level trigger new
> frame/line. Below page support my point if it is not wrong.
>
> http://www.arcadecollecting.com/info/Sync_fixing.txt
>
Tried to find the specific diagram in the spec on what CFG_INV_* means
but failed, can you help verified this with an oscilloscope and let know
the result? This is a fix then, and I'd like it to get into .32, sorry for late
reply.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-11-09 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 6:45 [PATCH 3/6] pxa: fix pxa168 lcd controller vsync/hsync timing error Jun Nie
2009-11-03 7:29 ` Jun Nie
2009-11-04 7:20 ` Eric Miao
2009-11-05 2:15 ` Jun Nie
2009-11-09 3:39 ` Eric Miao [this message]
2009-11-10 5:18 ` Jun Nie
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=f17812d70911081939nf30b893vc8a9b3cf821fc78@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=niej0001@gmail.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).