All of lore.kernel.org
 help / color / mirror / Atom feed
From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] imx-drm: Add mx6 hdmi transmitter support
Date: Thu, 31 Oct 2013 13:38:56 -0700	[thread overview]
Message-ID: <5272BFE0.5040409@boundarydevices.com> (raw)
In-Reply-To: <5272BC59.1080109@boundarydevices.com>

On 10/31/2013 1:23 PM, Troy Kisky wrote:
>
> +/* Workaround to clear the overflow condition */
> +static void imx_hdmi_clear_overflow(struct imx_hdmi *hdmi)
> +{
> +    int count;
> +    u8 val;
> +
> +    /* TMDS software reset */
> +    hdmi_writeb(hdmi, (u8)~HDMI_MC_SWRSTZ_TMDSSWRST_REQ, 
> HDMI_MC_SWRSTZ);
> +
> +    val = hdmi_readb(hdmi, HDMI_FC_INVIDCONF);
> +    if (hdmi->dev_type == IMX6DL_HDMI) {
> +        hdmi_writeb(hdmi, val, HDMI_FC_INVIDCONF);
> +        return;
> +    }
> +
> +    for (count = 0; count < 5; count++)
> +        hdmi_writeb(hdmi, val, HDMI_FC_INVIDCONF);
> +}
> +
>
> Hi Fabio,
>
> I get a magenta line down the left side of the screen unless I replace 
> the 5 with a 6.
> ie.
>
> +    for (count = 0; count < 6; count++)
> +        hdmi_writeb(hdmi, val, HDMI_FC_INVIDCONF);
>
>
> This is with a imx6q processor. With the 6, the picture looks great!
>
> Troy
>

It also works if I change the 5 to a 4! A 3 fails though.
To summarize:
0 works
1 fails
2 works
3 fails
4 works
5 fails
6 works
Very strange.

Troy

  reply	other threads:[~2013-10-31 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1383181127-12013-1-git-send-email-festevam@gmail.com>
2013-10-31 20:23 ` [PATCH v4] imx-drm: Add mx6 hdmi transmitter support Troy Kisky
2013-10-31 20:38   ` Troy Kisky [this message]
2013-10-31 20:45     ` Fabio Estevam
2013-10-31 21:00       ` Russell King - ARM Linux
2013-10-31 21:08         ` Fabio Estevam
2013-10-31 21:48           ` Matt Sealey
2013-11-04 23:20             ` Matt Sealey
2013-11-05  1:13               ` Fabio Estevam
2013-11-05 23:29                 ` Matt Sealey
2013-11-05 23:35                   ` Fabio Estevam
2013-11-05 23:59                     ` Matt Sealey

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=5272BFE0.5040409@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --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 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.