From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: Dove DT and HDMI on v3.16-rc1 (was: Re: [PATCH RFC 0/5] Dove PMU support)
Date: Wed, 18 Jun 2014 16:11:06 +0200 [thread overview]
Message-ID: <53A19DFA.7030207@gmail.com> (raw)
In-Reply-To: <20140615152554.GA13870@n2100.arm.linux.org.uk>
On 06/15/2014 05:25 PM, Russell King - ARM Linux wrote:
> As for DT, I should probably state that I'm far from happy with the DT
> situation on Dove. When I've tried it, I've encountered problems with
> the HDMI output - the picture spends more time blanked than displaying.
> I've no idea what is causing that, I've been through the SI5351
> registers, the TDA998x registers, the LCD controller registers, and I
> can't find any reason for it. Yet, boot the same kernel without DT
> and it works fine. Boot back using DT, and it's unstable again.
>
> I can't detect any difference on the actual HDMI signals themselves
> either. The HDMI clock seems stable and of the correct frequency.
>
> There is definitely some difference between booting with DT and booting
> with legacy stuff that seems to upset HDMI.
>
> For me, the /only/ reliably working system is one where DT is not
> involved. This means I remain opposed to any solutions which can't
> be used in a non-DT environment - at least until the HDMI issue can
> be resolved.
Russell,
as said on IRC, I really want this to be sorted out. I prepared a Dove
DT HDMI quick-hack and pushed it to
https://github.com/shesselba/linux-dove.git dove-drm-v3.16-rc1
Using your libdrm-armada and xf86-video-armada on Ubuntu raring armhf,
I can run Xfce4 on 1920x1080p60 on Dove Cubox without any blanking
issues. Using xrandr -s <mode> will fail after 2-3 times but that
shouldn't be related to the issues you see.
Please test above branch with kernel config at
https://dl.dropboxusercontent.com/u/59928252/config-dove-v3.16-rc1-hdmi
and report back if issues are still there.
Anyone having a Dove CuBox ready, please also test. Russell has a git
branch for the required video lib and drivers.
Sebastian
next prev parent reply other threads:[~2014-06-18 14:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 13:23 [PATCH RFC 0/5] Dove PMU support Russell King - ARM Linux
2014-04-27 13:28 ` [PATCH 1/5] pm: domains: quieten down generic pm domains Russell King
2014-04-30 23:46 ` Rafael J. Wysocki
2014-05-02 9:24 ` Ulf Hansson
2014-05-04 22:36 ` Rafael J. Wysocki
2015-02-13 11:54 ` Russell King - ARM Linux
2014-04-27 13:28 ` [PATCH 2/5] pm: domains: avoid potential oops in pm_genpd_remove_device() Russell King
2014-04-30 23:46 ` Rafael J. Wysocki
2014-04-27 13:29 ` [PATCH 3/5] ARM: dove: create a proper PMU driver for power domains, PMU IRQs and resets Russell King
2014-04-28 11:55 ` Ulf Hansson
2014-04-28 12:17 ` Russell King - ARM Linux
2015-02-13 13:29 ` Russell King - ARM Linux
2015-02-13 14:11 ` Russell King - ARM Linux
2015-02-13 16:12 ` Russell King - ARM Linux
2014-04-27 13:29 ` [PATCH 4/5] ARM: dove: add Dove PMU DT entries to dove.dtsi Russell King
2014-04-27 13:29 ` [PATCH 5/5] ARM: dove: add non-DT PMU support Russell King
2014-04-28 7:47 ` [PATCH RFC 0/5] Dove " Sebastian Hesselbarth
2014-04-28 8:31 ` Andrew Lunn
2014-04-29 9:15 ` Sebastian Hesselbarth
2014-06-15 15:25 ` Russell King - ARM Linux
2014-06-18 14:11 ` Sebastian Hesselbarth [this message]
2014-06-18 14:34 ` Dove DT and HDMI on v3.16-rc1 (was: Re: [PATCH RFC 0/5] Dove PMU support) Ezequiel Garcia
2014-06-18 15:01 ` Russell King - ARM Linux
2014-06-18 15:10 ` Dove DT and HDMI on v3.16-rc1 Sebastian Hesselbarth
2014-06-18 15:30 ` Russell King - ARM Linux
2014-06-18 15:39 ` Sebastian Hesselbarth
2014-06-18 15:59 ` Russell King - ARM Linux
2014-06-18 16:09 ` Dove DT and HDMI on v3.16-rc1 (was: Re: [PATCH RFC 0/5] Dove PMU support) Nicolas Pitre
2014-06-21 19:39 ` Ezequiel Garcia
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=53A19DFA.7030207@gmail.com \
--to=sebastian.hesselbarth@gmail.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 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).