From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Fabio Estevam <festevam@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH] imx-drm: imx-hdmi: fix hdmi hotplug detection initial state
Date: Mon, 9 Jun 2014 18:49:41 +0100 [thread overview]
Message-ID: <20140609174941.GS23430@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5AJsBR6qpf0yhnm-75Q9bg8ek1a2CQWpkxnQDL-OqAWvg@mail.gmail.com>
On Mon, Jun 09, 2014 at 11:29:28AM -0300, Fabio Estevam wrote:
> On Mon, Jun 9, 2014 at 11:06 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>
> > Please check the status in /sys/class/drm/card0-HDMI-A-1/status. This
> > should report the current state of the hotplug detection.
>
> /sys/class/drm/card0-HDMI-A-1/status returns the correct state for
> HDMI cable connection.
Good, so that means we're reporting the correct status to the DRM layer.
Please post the kernel boot messages, one with the HDMI cable disconnected,
and one with a HDMI sink connected.
> The HDMI undetected issue I am seeing on sabresd seems to be related
> to the simultaneous usage of HDMI and LVDS.
>
> If I remove the ldb node from the imx6qdl-sabresd.dtsi, then the HDMI
> cable is correctly detected and HDMI is shown right after boot.
I wonder if the problem is that HDMI and LVDS are interfering with each
other wrt the required pixel clock, and LVDS is winning. If we have
HDMI enabled, many HDMI sinks will only work if we set one of their
supported modes (with the dot clock within 1% - though some sinks are
more lenient).
I think the Novena people have run into this issue, but I've not seen
much in the way of contributions back, despite them making use of my
patches...
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-09 17:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 13:56 [PATCH] imx-drm: imx-hdmi: fix hdmi hotplug detection initial state Russell King
2014-06-06 14:06 ` Greg Kroah-Hartman
2014-06-09 13:44 ` Fabio Estevam
2014-06-09 14:06 ` Russell King - ARM Linux
2014-06-09 14:29 ` Fabio Estevam
2014-06-09 14:33 ` Shawn Guo
2014-06-09 15:19 ` Fabio Estevam
2014-06-09 17:49 ` Russell King - ARM Linux [this message]
2014-06-09 18:15 ` Fabio Estevam
2014-06-09 18:38 ` Fabio Estevam
2014-06-09 18:47 ` Fabio Estevam
2014-06-09 20:09 ` Russell King - ARM Linux
2014-06-09 21:03 ` Fabio Estevam
2014-06-10 12:58 ` Fabio Estevam
2014-06-10 13:32 ` Fabio Estevam
2014-06-11 8:17 ` Russell King - ARM Linux
2014-06-11 15:34 ` Philipp Zabel
2014-06-16 14:13 ` Fabio Estevam
2014-06-16 21:49 ` Russell King - ARM Linux
2014-06-10 15:13 ` Russell King - ARM Linux
2014-06-10 16:14 ` Russell King - ARM Linux
2014-06-10 17:04 ` Russell King - ARM Linux
2014-06-10 17:36 ` Fabio Estevam
2014-06-09 19:29 ` Russell King - ARM Linux
2014-06-09 19:29 ` Russell King - ARM Linux
2014-06-10 18:54 ` Tim Harvey
2014-06-10 19:03 ` Fabio Estevam
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=20140609174941.GS23430@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=shawn.guo@freescale.com \
/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).