linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: imx-drm: Add HDMI support
Date: Mon, 21 Oct 2013 14:17:58 +0100	[thread overview]
Message-ID: <20131021131758.GA25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131021123652.GN17165@S2101-09.ap.freescale.net>

On Mon, Oct 21, 2013 at 08:36:55PM +0800, Shawn Guo wrote:
> On Mon, Oct 21, 2013 at 10:34:48AM +0100, Russell King - ARM Linux wrote:
> > However, the IPU is more stable with switching to bypass while it relocks
> > than not.
> 
> As far as I know, FSL kernel has always been doing relock without
> switching to bypass, and I haven't heard unstable IPU issue from their
> testing.  Do you have a case that I can set up here to see the issue?

export DISPLAY=:0
while :; do
  xrandr -s 1280x720 -r 50
  sleep 5
  xrandr -s 1280x720 -r 60
  sleep 5
done

is one way.  Another way is to switch between all possible resolutions
supported by the connected device, keeping each resolution for 30 seconds
a time.  Normally after one or two run-throughs, the IPU will be deader
than the parrot in Monty Python's parrot sketch, requiring a reboot to
get it working again.

As I've said previously, when it gets into this state, all the status
registers I can find report that all FIFOs in the IPU are sitting in
their empty state.  The TMDS clock is correct, and the frame composer
in the HDMI block is working, but it's not producing any sync signals or
pixel data.

  reply	other threads:[~2013-10-21 13:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52602EEA.6060402@prisktech.co.nz>
2013-10-17 19:39 ` imx-drm: Add HDMI support Russell King - ARM Linux
2013-10-17 19:52   ` Alexander Shiyan
2013-10-17 20:35     ` Russell King - ARM Linux
2013-10-19 12:12       ` Russell King - ARM Linux
2013-10-21  9:13         ` Shawn Guo
2013-10-21  9:34           ` Russell King - ARM Linux
2013-10-21 12:36             ` Shawn Guo
2013-10-21 13:17               ` Russell King - ARM Linux [this message]
2013-10-30  8:34                 ` Shawn Guo
2013-10-30 18:01     ` Matt Sealey
2013-10-30 19:01       ` Russell King - ARM Linux
2013-11-05 22:39         ` Matt Sealey
2013-11-07 17:29           ` Russell King - ARM Linux
2013-11-09  0:23             ` Matt Sealey
2013-11-09  0:53               ` Russell King - ARM Linux
2013-11-09  6:11                 ` Matt Sealey
2013-11-09 10:28                   ` Russell King - ARM Linux
2013-10-19 15:55 ` Russell King - ARM Linux

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=20131021131758.GA25034@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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).