From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] sunxi: video: Force h/vsync active high when using ext. vga dac on some boards
Date: Wed, 28 Jan 2015 15:42:26 +0100 [thread overview]
Message-ID: <54C8F552.2010204@redhat.com> (raw)
In-Reply-To: <1422446756.14124.9.camel@hellion.org.uk>
Hi,
On 28-01-15 13:05, Ian Campbell wrote:
> On Wed, 2015-01-28 at 11:47 +0100, Hans de Goede wrote:
>> On both my A13-OLinuxIno and my A13-OLinuxIno-Micro, the vga output gives an
>> unstable image when active low v or hsync is used.
>>
>> The problem seems to be specific to the OLinuxIno A13 (normal & micro)
>> boards. I've just looked up the schematics and they use an opendrain driver
>> for the vga sync lines, and with sync pulses it is the logical high->low
>> edge of the pulse which counts for the timing, which with an active low
>> sync is being driven by the pull-up, and that simply seems to not drive
>> it hard enough to get a stable image.
>>
>> So force v and hsync active high on these boards. independent of what the
>> modeline says. This fixes the unstable image.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> Acked-by: Ian Campbell <ijc@hellion.org.uk>
Thanks.
> Although I might have been tempted to adjust mode->sync in the caller or
> the place which populates it in the first place, just due to a general
> dislike of boolean params to functions (which are opaque at the caller)
> and to keep mode in sync with reality (if that matters).
I had the same idea, but mode can point to the global fixed mode list, so
it is: "const struct ctfb_res_modes *mode" and we cannot change what a const
pointer points too.
Regards,
Hans
next prev parent reply other threads:[~2015-01-28 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 10:47 [U-Boot] [PATCH v2] sunxi: video: Force h/vsync active high when using ext. vga dac on some boards Hans de Goede
2015-01-28 12:05 ` Ian Campbell
2015-01-28 14:42 ` Hans de Goede [this message]
2015-01-28 15:33 ` Ian Campbell
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=54C8F552.2010204@redhat.com \
--to=hdegoede@redhat.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.