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>,
Tim Harvey <tharvey@gateworks.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Philipp Zabel <philipp.zabel@gmail.com>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH] imx-drm: imx-hdmi: fix hdmi hotplug detection initial state
Date: Mon, 9 Jun 2014 20:29:03 +0100 [thread overview]
Message-ID: <20140609192902.GT23430@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5AdKJuUkxP29yp7cdxjXtNdRub0f5eRwKN4DZq4dh6m6w@mail.gmail.com>
On Mon, Jun 09, 2014 at 03:15:16PM -0300, Fabio Estevam wrote:
> With HDMI cable connected (no image is seen on HDMI, only on lvds cable):
>
> imx-drm display-subsystem.11: bound 120000.hdmi (ops hdmi_ops)
> imx-hdmi 120000.hdmi: EVENT=plugin
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 0
Right, so it does know that the HDMI sink is connected...
> imx-drm display-subsystem.11: bound ldb.10 (ops imx_ldb_ops)
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: got edid: width[51] x height[28]
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 138500000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 138500000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
And the mode it's setting has a pixel clock frequency of 138.5MHz here.
> If I disconnect/reconnect the HDMI cable (then image is seen on both
> HDMI and LVDS):
>
> root@freescale /$ imx-hdmi 120000.hdmi: EVENT=plugout
> imx-hdmi 120000.hdmi: EVENT=plugin
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 138500000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: got edid: width[51] x height[28]
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 138500000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 138500000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
And here it again configures 138.5MHz pixel clock - same as above. So,
from this we can't see any difference in the setup, and we can say that
it's not mode->clock which is the problem.
> Now booting the kernel with HDMI disconnected:
>
> imx-hdmi 120000.hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
> imx-hdmi 120000.hdmi: hdmi_set_clk_regenerator: samplerate=48000
> ratio=100 pixelclk=74250000 N=6144 cts=74250
> imx-drm display-subsystem.11: bound 120000.hdmi (ops hdmi_ops)
Right, so here it knows that there's nothing connected.
> imx-drm display-subsystem.11: bound ldb.10 (ops imx_ldb_ops)
> Console: switching to colour frame buffer device 128x48
So it selects an initial mode based upon the LVDS device configuration.
> And after connecting the HDMI cable:
>
> imx-hdmi 120000.hdmi: EVENT=plugin
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 0
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: got edid: width[51] x height[28]
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 78800000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
> imx-hdmi 120000.hdmi: Non-CEA mode used in HDMI
> imx-hdmi 120000.hdmi: final pixclk = 78800000
> imx-hdmi 120000.hdmi: imx_hdmi_setup DVI mode
>
> Image is seen on both LVDS and HDMI monitor, but HDMI resolution is
> not correct (this is a different bug though).
I'm guessing that here, DRM kept the original configuration rather than
selecting one appropriate to the newly connected device.
--
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 19:29 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
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 [this message]
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=20140609192902.GT23430@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=philipp.zabel@gmail.com \
--cc=shawn.guo@freescale.com \
--cc=tharvey@gateworks.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).