From: Darren Etheridge <detheridge@ti.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: linux@arm.linux.org.uk, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/tilcdc drm/i2c/tda998x workaround for sync issues on TI SoC
Date: Thu, 1 Aug 2013 09:29:00 -0500 [thread overview]
Message-ID: <20130801142900.GA17271@ti.com> (raw)
In-Reply-To: <51F971C0.1030408@gmail.com>
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote on Wed [2013-Jul-31 22:21:20 +0200]:
> Darren,
>
> I now fully understand the issues of AM335x's LCD controller and your
> fix for it. I suggest to clarify the comments you added to tilcdc to
> allow others to understand it more quickly.
>
Sebastian,
Thanks for looking at my proposed changes, you understand this sync
stuff very well so I appreciate your input that this is actually an
acceptable workaround.
> Actually, the LCD controller always aligns vsync to the second edge
> of hsync, which will never give VESA-compliant sync. The (elegant)
> workaround you are proposing is to align both rising edges, so at
> least TDA998x can sync on those with some hskew added. Lucky you that
> it ignores hsync length but only looks for rising HS/VS edges ;)
Yes we definitely got lucky with this one, good thing the NXP
supported that reference pixel position, as I was out of options from
the lcd controller side of things to adjust the horizontal position.
>
> Should we prepare a new patch set comprising the following patches?
>
> Russell King:
> drm/i2c: nxp-tda998x: fix EDID reading on TDA19988 devices
> drm/i2c: nxp-tda998x: ensure VIP output mux is properly set
> drm/i2c: nxp-tda998x: fix npix/nline programming
> drm/i2c: nxp-tda998x: prepare for video input configuration
> drm/i2c: nxp-tda998x: add video and audio input configuration
>
> Sebastian Hesselbarth:
> drm/i2c: tda998x: fix sync generation and calculation
>
> Darren Etheridge:
> drm/i2c/tda998x prepare for tilcdc sync workaround
> drm/tilcdc fixup mode to workaound sync for tda998x
>
> Or do we keep them separated and possibly resend them if David cannot
> find them anymore?
I vote we submit a complete series that we can all test, there were quite
a lot of versions of things in flight at the same time so I am sure
David would appreciate a consolidated version.
The only thing I have not tested is audio support, but as the original
driver did not have that anyway I don't consider it blocking if it is
working for CuBox.
Darren
next prev parent reply other threads:[~2013-08-01 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 18:32 [PATCH 0/2] drm/tilcdc drm/i2c/tda998x workaround for sync issues on TI SoC Darren Etheridge
2013-07-25 18:32 ` [PATCH 1/2] drm/i2c/tda998x prepare for tilcdc sync workaround Darren Etheridge
2013-07-25 18:32 ` [PATCH 2/2] drm/tilcdc fixup mode to workaound sync for tda998x Darren Etheridge
2013-07-25 19:32 ` [PATCH 0/2] drm/tilcdc drm/i2c/tda998x workaround for sync issues on TI SoC Rob Clark
2013-07-30 7:36 ` Sebastian Hesselbarth
2013-07-31 20:21 ` Sebastian Hesselbarth
2013-07-31 20:28 ` Russell King - ARM Linux
2013-08-01 14:29 ` Darren Etheridge [this message]
2013-08-01 15:19 ` Rob Clark
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=20130801142900.GA17271@ti.com \
--to=detheridge@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux@arm.linux.org.uk \
--cc=sebastian.hesselbarth@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