From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] imx-drm: Add mx6 hdmi transmitter support
Date: Sun, 20 Oct 2013 10:32:34 +0100 [thread overview]
Message-ID: <20131020093233.GM25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131016183107.GC18050@kroah.com>
Another problem.
After performing several modesets, the IPU seems to lock up and produce
no syncs or output data.
I've seen this many times over the last week while testing out various
aspects of imx-drm, and had put it down to problems with the clocking
arrangement getting its settings wrong. Now that I've sorted all that
though, and I still have the problem, there's something else going on.
What I see is:
- the HDMI clock is running correctly (right frequency and unmodulated)
- the TMDS data lines show signs of there being some data (probably
control, guard bands and data islands from the frame composer in the
HDMI interface). The data lines are definitely lacking image data though.
- reading the various status registers indicates that all FIFOs within
the IPU are empty.
- the attached TV says that there is no HDMI signal.
One of my tests has been to cycle through all display resolutions from the
smallest width to the largest, leaving each one set for 30 seconds. This
will occasionally provoke the problem, but obviously is rather slow to do
so.
I tried this with a less demanding test last night as far as a change in
the settings: switching between 720p at 50 and 60Hz. The clocks for these
two modes are the same at 74.25MHz, and the vertical timing parameters are
identical. The only timing difference is with the horizontal parameters:
1280x720 (0x41) 74.2MHz +HSync +VSync +preferred
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
v: height 720 start 725 end 730 total 750 clock 60.0Hz
1280x720 (0x4f) 74.2MHz +HSync +VSync
h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
v: height 720 start 725 end 730 total 750 clock 50.0Hz
This dies within a couple of minutes. I haven't gathered enough
information to tell whether it always dies when switching from 50 -> 60Hz
or whether it's any switch.
My test for this is basically:
while :; do
xrandr -s 1280x720 -r 50
sleep 5
xrandr -s 1280x720 -r 60
sleep 5
done
next prev parent reply other threads:[~2013-10-20 9:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380826287-30253-1-git-send-email-fabio.estevam@freescale.com>
2013-10-03 18:51 ` [PATCH v2 2/3] ARM: dts: imx6qdl-wandboard: Add HDMI support Fabio Estevam
2013-10-14 17:38 ` Russell King - ARM Linux
2013-10-15 2:47 ` Fabio Estevam
2013-10-15 10:00 ` Russell King - ARM Linux
2013-10-15 10:09 ` Sascha Hauer
2013-10-14 17:40 ` Russell King - ARM Linux
2013-10-14 22:50 ` Russell King - ARM Linux
2013-10-15 3:20 ` Fabio Estevam
2013-10-15 7:46 ` Sascha Hauer
2013-10-15 9:18 ` Russell King - ARM Linux
2013-10-15 10:35 ` Russell King - ARM Linux
2013-10-16 7:20 ` Sascha Hauer
2013-10-03 18:51 ` [PATCH v2 3/3] ARM: dts: imx6qdl-sabresd: " Fabio Estevam
2013-10-03 20:27 ` [PATCH v2 1/3] imx-drm: Add mx6 hdmi transmitter support Dan Carpenter
2013-10-15 13:10 ` Russell King - ARM Linux
2013-10-15 13:17 ` Fabio Estevam
2013-10-16 17:03 ` Russell King - ARM Linux
2013-10-16 18:07 ` Russell King - ARM Linux
2013-10-16 18:31 ` Greg Kroah-Hartman
2013-10-16 19:02 ` Russell King - ARM Linux
2013-10-16 21:20 ` Sascha Hauer
2013-10-17 8:27 ` Lucas Stach
2013-10-20 0:04 ` Russell King - ARM Linux
2013-10-20 13:00 ` Russell King - ARM Linux
2013-10-20 16:31 ` Russell King - ARM Linux
2013-10-20 21:56 ` Russell King - ARM Linux
2013-10-20 9:32 ` Russell King - ARM Linux [this message]
2013-10-16 19:37 ` Troy Kisky
2013-10-16 20:27 ` Russell King - ARM Linux
2013-10-16 21:03 ` Troy Kisky
2013-10-16 22:27 ` Russell King - ARM Linux
2013-10-17 8:45 ` Russell King - ARM Linux
2013-10-03 20:48 ` Greg KH
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=20131020093233.GM25034@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).