All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Darren Etheridge <detheridge@ti.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: Wed, 31 Jul 2013 22:21:20 +0200	[thread overview]
Message-ID: <51F971C0.1030408@gmail.com> (raw)
In-Reply-To: <CAF6AEGteMTuVLjx7zz1Rb-qXKwX2upKNt-guUO9PSAoN_SKipw@mail.gmail.com>

On 07/25/2013 09:32 PM, Rob Clark wrote:
> On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge <detheridge@ti.com> wrote:
[...]
>> This patch set inverts the hsync signal coming from the tilcdc so the NXP
>> is kept happy and then shifts the output to the right to compensate for the
>> sync timing issues.  Display modes from the NXP have been verified using a
>> HDMI analyzer and are reporting correct timings at the output stage.
>>
>> Hopefully this will allow the dove/tda driver changes to progress now that
>> were blocked as per this discussion:
>> http://lists.freedesktop.org/archives/dri-devel/2013-July/040900.html
>>
>
> Good find Darren!  The patches look good to me from a quick review.
> It would be good to get a tested-by from someone on cubox, but it is
> good that we finally found the issue so that we can unblock further
> tda998x development.

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.

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 ;)

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?

Sebastian

  parent reply	other threads:[~2013-07-31 20:21 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 [this message]
2013-07-31 20:28     ` Russell King - ARM Linux
2013-08-01 14:29     ` Darren Etheridge
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=51F971C0.1030408@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=detheridge@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux@arm.linux.org.uk \
    /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.