All of lore.kernel.org
 help / color / mirror / Atom feed
* No HDMI video on imx6qsabresd with dizzy
@ 2014-11-12 22:58 Nikolay Dimitrov
  2014-11-12 23:02 ` Fabio Estevam
  2014-11-13  9:29 ` Andreas Müller
  0 siblings, 2 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-12 22:58 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

Hi guys,

I'm trying to use unmodified dizzy build with imx6q sabresd, for
testing video playback. U-Boot outputs HDMI image during boot, but in
Linux there's no HDMI image (no console, no video playback).

The image is "fsl-image-multimedia-full", kernel 3.10.17. The device
files /dev/video* and /dev/fb* are available, but gstreamer playback
doesn't output any image on the HDMI port (seems to be stuck instead of
playing).

The kernel cmdline doesn't specify any video settings, which typically
is an issue, but when I add the video bootargs:

...video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24...

The board stops to print any boot messages after "Starting kernel..."
and seems to be stuck. Removing the video bootargs allows again to boot
normally.

I must admit that I'm somewhat puzzled by this behavior, as I already
have daizy running with 3.10.17 on a custom board, and the video is
working there with almost the same bootargs. Do you guys have any ideas
for how to configure imx6q sabresd for HDMI video?

Thanks in advance. Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-12 22:58 No HDMI video on imx6qsabresd with dizzy Nikolay Dimitrov
@ 2014-11-12 23:02 ` Fabio Estevam
  2014-11-13 10:30   ` Daiane Angolini
  2014-11-13 15:10   ` Nikolay Dimitrov
  2014-11-13  9:29 ` Andreas Müller
  1 sibling, 2 replies; 17+ messages in thread
From: Fabio Estevam @ 2014-11-12 23:02 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

On Wed, Nov 12, 2014 at 8:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> Hi guys,
>
> I'm trying to use unmodified dizzy build with imx6q sabresd, for
> testing video playback. U-Boot outputs HDMI image during boot, but in
> Linux there's no HDMI image (no console, no video playback).

It looks like a HDMI driver bug from 3.10.17. Please disable HDMI
support in U-boot and try again.


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-12 22:58 No HDMI video on imx6qsabresd with dizzy Nikolay Dimitrov
  2014-11-12 23:02 ` Fabio Estevam
@ 2014-11-13  9:29 ` Andreas Müller
  2014-11-13 15:17   ` Nikolay Dimitrov
  1 sibling, 1 reply; 17+ messages in thread
From: Andreas Müller @ 2014-11-13  9:29 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

On Wed, Nov 12, 2014 at 11:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> Hi guys,
>
> I'm trying to use unmodified dizzy build with imx6q sabresd, for
> testing video playback. U-Boot outputs HDMI image during boot, but in
> Linux there's no HDMI image (no console, no video playback).
>
> The image is "fsl-image-multimedia-full", kernel 3.10.17. The device
> files /dev/video* and /dev/fb* are available, but gstreamer playback
> doesn't output any image on the HDMI port (seems to be stuck instead of
> playing).
>
> The kernel cmdline doesn't specify any video settings, which typically
> is an issue, but when I add the video bootargs:
>
> ...video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24...
>
> The board stops to print any boot messages after "Starting kernel..."
> and seems to be stuck. Removing the video bootargs allows again to boot
> normally.
>
> I must admit that I'm somewhat puzzled by this behavior, as I already
> have daizy running with 3.10.17 on a custom board, and the video is
> working there with almost the same bootargs. Do you guys have any ideas
> for how to configure imx6q sabresd for HDMI video?
>
> Thanks in advance. Regards,
> Nikolay
> --
Had same here.

I think there are two problems:
* 3.10.17 EDID decoding works only for monitors with EDID extended
blocks (patch 0001..)
* 1024x768 is not a CEA mode. If I read the code of 3.10.17 correct,
HDMI supports only modes which are found in
drivers/video/mxc/mxc_edid.c const struct fb_videomode
mxc_cea_mode[64]. I hacked up working solution (patch 0002..). Note
that this is just a hack - it might lead to incorrect colour space
conversion or wrong PixelRepetitionOutput (see mxc_hdmi_setup:
hdmi->vic is always 0 for my patches).

These patches were tested with two monitors (1280x1024 / 1650x<I
forgot>) and seem to work fine.

Hope it wipes away your problem

Andreas

[-- Attachment #2: 0001-mxc_hdmi.c-parse-EDID-extensions-only-in-case-monito.patch --]
[-- Type: text/x-patch, Size: 1679 bytes --]

From 28d25d88aef778162b989000b87fe54fd3660242 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andreas=20M=C3=BCller?= <schnitzeltony@googlemail.com>
Date: Thu, 6 Nov 2014 10:23:01 +0100
Subject: [PATCH 1/4] mxc_hdmi.c: parse EDID extensions only in case monitor
 supports them
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

For monitor not supporting extensions I get:

[    0.829299] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
[    0.960509] mxc_hdmi 20e0000.hdmi_video: Read EDID again
[    0.960522] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
[    1.091703] mxc_hdmi 20e0000.hdmi_video: No modes read from edid
[    1.091714] mxc_hdmi 20e0000.hdmi_video: create default modelist

and have only 640x480 screen resolution.

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
---
 drivers/video/mxc/mxc_hdmi.c | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/drivers/video/mxc/mxc_hdmi.c b/drivers/video/mxc/mxc_hdmi.c
index e510025..8ea7d0d 100644
--- a/drivers/video/mxc/mxc_hdmi.c
+++ b/drivers/video/mxc/mxc_hdmi.c
@@ -1577,10 +1577,13 @@ static int mxc_edid_read_internal(struct mxc_hdmi *hdmi, unsigned char *edid,
 	memset(&fbi->monspecs, 0, sizeof(fbi->monspecs));
 	fb_edid_to_monspecs(edid, &fbi->monspecs);
 
-	ret = mxc_edid_parse_ext_blk(edid + EDID_LENGTH,
-			cfg, &fbi->monspecs);
-	if (ret < 0)
-		return -ENOENT;
+	/* edid extension blocks parsing */
+	if (extblknum > 0) {
+		ret = mxc_edid_parse_ext_blk(edid + EDID_LENGTH,
+				cfg, &fbi->monspecs);
+		if (ret < 0)
+			return -ENOENT;
+	}
 
 	/* need read segment block? */
 	if (extblknum > 1) {
-- 
1.8.3.1


[-- Attachment #3: 0002-mxc_hdmi-allow-EDID-to-select-non-CEA-modes.patch --]
[-- Type: text/x-patch, Size: 1533 bytes --]

From 06d5731300357b0ff3547acdf26419088d5b3510 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andreas=20M=C3=BCller?= <schnitzeltony@googlemail.com>
Date: Fri, 7 Nov 2014 10:55:09 +0100
Subject: [PATCH 2/4] mxc_hdmi: allow EDID to select non CEA modes
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
---
 drivers/video/mxc/mxc_hdmi.c | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/drivers/video/mxc/mxc_hdmi.c b/drivers/video/mxc/mxc_hdmi.c
index 8ea7d0d..8352248 100644
--- a/drivers/video/mxc/mxc_hdmi.c
+++ b/drivers/video/mxc/mxc_hdmi.c
@@ -71,9 +71,6 @@
 #define HDMI_EDID_SAME		-2
 #define HDMI_EDID_NO_MODES	-3
 
-#define NUM_CEA_VIDEO_MODES	64
-#define DEFAULT_VIDEO_MODE	16 /* 1080P */
-
 #define RGB			0
 #define YCBCR444		1
 #define YCBCR422_16BITS		2
@@ -1798,13 +1795,13 @@ static void mxc_hdmi_edid_rebuild_modelist(struct mxc_hdmi *hdmi)
 		/*
 		 * We might check here if mode is supported by HDMI.
 		 * We do not currently support interlaced modes.
-		 * And add CEA modes in the modelist.
 		 */
 		mode = &hdmi->fbi->monspecs.modedb[i];
 
 		if (!(mode->vmode & FB_VMODE_INTERLACED) &&
-				(mxc_edid_mode_to_vic(mode) != 0)) {
-
+				mode->xres <= 1920 &&
+				mode->yres <= 1080 &&
+				mode->flag & FB_MODE_IS_STANDARD) {
 			dev_dbg(&hdmi->pdev->dev, "Added mode %d:", i);
 			dev_dbg(&hdmi->pdev->dev,
 				"xres = %d, yres = %d, freq = %d, vmode = %d, flag = %d\n",
-- 
1.8.3.1


^ permalink raw reply related	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-12 23:02 ` Fabio Estevam
@ 2014-11-13 10:30   ` Daiane Angolini
  2014-11-13 15:18     ` Nikolay Dimitrov
  2014-11-13 15:10   ` Nikolay Dimitrov
  1 sibling, 1 reply; 17+ messages in thread
From: Daiane Angolini @ 2014-11-13 10:30 UTC (permalink / raw)
  To: Fabio Estevam; +Cc: meta-freescale@yoctoproject.org

On Wed, Nov 12, 2014 at 9:02 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Nov 12, 2014 at 8:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi guys,
>>
>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>> testing video playback. U-Boot outputs HDMI image during boot, but in
>> Linux there's no HDMI image (no console, no video playback).
>
> It looks like a HDMI driver bug from 3.10.17. Please disable HDMI
> support in U-boot and try again.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6703
Daiane

> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-12 23:02 ` Fabio Estevam
  2014-11-13 10:30   ` Daiane Angolini
@ 2014-11-13 15:10   ` Nikolay Dimitrov
  2014-11-13 17:46     ` Nikolay Dimitrov
  1 sibling, 1 reply; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 15:10 UTC (permalink / raw)
  To: Fabio Estevam; +Cc: meta-freescale@yoctoproject.org

Hi Fabio,

On 11/13/2014 01:02 AM, Fabio Estevam wrote:
> On Wed, Nov 12, 2014 at 8:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi guys,
>>
>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>> testing video playback. U-Boot outputs HDMI image during boot, but in
>> Linux there's no HDMI image (no console, no video playback).
>
> It looks like a HDMI driver bug from 3.10.17. Please disable HDMI
> support in U-boot and try again.

Thanks, I'll try and share the outcome.

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13  9:29 ` Andreas Müller
@ 2014-11-13 15:17   ` Nikolay Dimitrov
  2014-11-13 15:48     ` Andreas Müller
  0 siblings, 1 reply; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 15:17 UTC (permalink / raw)
  To: Andreas Müller; +Cc: meta-freescale@yoctoproject.org

Hi Andreas,

On 11/13/2014 11:29 AM, Andreas Müller wrote:
> On Wed, Nov 12, 2014 at 11:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi guys,
>>
>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>> testing video playback. U-Boot outputs HDMI image during boot, but in
>> Linux there's no HDMI image (no console, no video playback).
>>
>> The image is "fsl-image-multimedia-full", kernel 3.10.17. The device
>> files /dev/video* and /dev/fb* are available, but gstreamer playback
>> doesn't output any image on the HDMI port (seems to be stuck instead of
>> playing).
>>
>> The kernel cmdline doesn't specify any video settings, which typically
>> is an issue, but when I add the video bootargs:
>>
>> ...video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24...
>>
>> The board stops to print any boot messages after "Starting kernel..."
>> and seems to be stuck. Removing the video bootargs allows again to boot
>> normally.
>>
>> I must admit that I'm somewhat puzzled by this behavior, as I already
>> have daizy running with 3.10.17 on a custom board, and the video is
>> working there with almost the same bootargs. Do you guys have any ideas
>> for how to configure imx6q sabresd for HDMI video?
>>
>> Thanks in advance. Regards,
>> Nikolay
>> --
> Had same here.
>
> I think there are two problems:
> * 3.10.17 EDID decoding works only for monitors with EDID extended
> blocks (patch 0001..)
> * 1024x768 is not a CEA mode. If I read the code of 3.10.17 correct,
> HDMI supports only modes which are found in
> drivers/video/mxc/mxc_edid.c const struct fb_videomode
> mxc_cea_mode[64]. I hacked up working solution (patch 0002..). Note
> that this is just a hack - it might lead to incorrect colour space
> conversion or wrong PixelRepetitionOutput (see mxc_hdmi_setup:
> hdmi->vic is always 0 for my patches).
>
> These patches were tested with two monitors (1280x1024 / 1650x<I
> forgot>) and seem to work fine.

Thanks for your detailed answer. I remember seeing discussions on the
net about a safe fallback resolution for imx6 hdmi, so that's the only
reason to choose 1024x768.

Also, are you sure that the HDMI code doesn't use the CVT (Common VESA
Table) resolutions? Need to check this. I'll also look a the code
which you pointed me to, and try your patches.

I'm not looking for big or pixel-exact resolutions on HDMI, just some
reasonable resolution so I can test my gstreamer issues there :).

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 10:30   ` Daiane Angolini
@ 2014-11-13 15:18     ` Nikolay Dimitrov
  0 siblings, 0 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 15:18 UTC (permalink / raw)
  To: Daiane Angolini, Fabio Estevam; +Cc: meta-freescale@yoctoproject.org

Thanks Diane!

On 11/13/2014 12:30 PM, Daiane Angolini wrote:
> On Wed, Nov 12, 2014 at 9:02 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Wed, Nov 12, 2014 at 8:58 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>>> Hi guys,
>>>
>>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>>> testing video playback. U-Boot outputs HDMI image during boot, but in
>>> Linux there's no HDMI image (no console, no video playback).
>>
>> It looks like a HDMI driver bug from 3.10.17. Please disable HDMI
>> support in U-boot and try again.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6703
> Daiane

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 15:17   ` Nikolay Dimitrov
@ 2014-11-13 15:48     ` Andreas Müller
  2014-11-13 17:50       ` Nikolay Dimitrov
  0 siblings, 1 reply; 17+ messages in thread
From: Andreas Müller @ 2014-11-13 15:48 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

On Thu, Nov 13, 2014 at 4:17 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> Hi Andreas,
>
>
> On 11/13/2014 11:29 AM, Andreas Müller wrote:
>>
>> On Wed, Nov 12, 2014 at 11:58 PM, Nikolay Dimitrov <picmaster@mail.bg>
>> wrote:
>>>
>>> Hi guys,
>>>
>>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>>> testing video playback. U-Boot outputs HDMI image during boot, but in
>>> Linux there's no HDMI image (no console, no video playback).
>>>
>>> The image is "fsl-image-multimedia-full", kernel 3.10.17. The device
>>> files /dev/video* and /dev/fb* are available, but gstreamer playback
>>> doesn't output any image on the HDMI port (seems to be stuck instead of
>>> playing).
>>>
>>> The kernel cmdline doesn't specify any video settings, which typically
>>> is an issue, but when I add the video bootargs:
>>>
>>> ...video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24...
>>>
>>> The board stops to print any boot messages after "Starting kernel..."
>>> and seems to be stuck. Removing the video bootargs allows again to boot
>>> normally.
>>>
>>> I must admit that I'm somewhat puzzled by this behavior, as I already
>>> have daizy running with 3.10.17 on a custom board, and the video is
>>> working there with almost the same bootargs. Do you guys have any ideas
>>> for how to configure imx6q sabresd for HDMI video?
>>>
>>> Thanks in advance. Regards,
>>> Nikolay
>>> --
>>
>> Had same here.
>>
>> I think there are two problems:
>> * 3.10.17 EDID decoding works only for monitors with EDID extended
>> blocks (patch 0001..)
>> * 1024x768 is not a CEA mode. If I read the code of 3.10.17 correct,
>> HDMI supports only modes which are found in
>> drivers/video/mxc/mxc_edid.c const struct fb_videomode
>> mxc_cea_mode[64]. I hacked up working solution (patch 0002..). Note
>> that this is just a hack - it might lead to incorrect colour space
>> conversion or wrong PixelRepetitionOutput (see mxc_hdmi_setup:
>> hdmi->vic is always 0 for my patches).
>>
>> These patches were tested with two monitors (1280x1024 / 1650x<I
>> forgot>) and seem to work fine.
>
>
> Thanks for your detailed answer. I remember seeing discussions on the
> net about a safe fallback resolution for imx6 hdmi, so that's the only
> reason to choose 1024x768.
>
> Also, are you sure that the HDMI code doesn't use the CVT (Common VESA
> Table) resolutions? Need to check this. I'll also look a the code
> which you pointed me to, and try your patches.
>
> I'm not looking for big or pixel-exact resolutions on HDMI, just some
> reasonable resolution so I can test my gstreamer issues there :).
>
> Regards,
> Nikolay
After re reading this thread I saw that my patches are addressing a
different problem. In short: Whatever monitor I connected to HDMI (via
DVI) I got only 640x480 and complaints like

[    0.829299] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
[    0.960509] mxc_hdmi 20e0000.hdmi_video: Read EDID again
[    0.960522] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
[    1.091703] mxc_hdmi 20e0000.hdmi_video: No modes read from edid
[    1.091714] mxc_hdmi 20e0000.hdmi_video: create default modelist

Andreas


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 15:10   ` Nikolay Dimitrov
@ 2014-11-13 17:46     ` Nikolay Dimitrov
  2014-11-13 19:34       ` Nikolay Dimitrov
  0 siblings, 1 reply; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 17:46 UTC (permalink / raw)
  To: Fabio Estevam; +Cc: meta-freescale@yoctoproject.org

Hi Fabio,

On 11/13/2014 05:10 PM, Nikolay Dimitrov wrote:
> Hi Fabio,
>
> On 11/13/2014 01:02 AM, Fabio Estevam wrote:
>> On Wed, Nov 12, 2014 at 8:58 PM, Nikolay Dimitrov <picmaster@mail.bg>
>> wrote:
>>> Hi guys,
>>>
>>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>>> testing video playback. U-Boot outputs HDMI image during boot, but in
>>> Linux there's no HDMI image (no console, no video playback).
>>
>> It looks like a HDMI driver bug from 3.10.17. Please disable HDMI
>> support in U-boot and try again.
>
> Thanks, I'll try and share the outcome.

This suggestion worked OK, thanks!

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 15:48     ` Andreas Müller
@ 2014-11-13 17:50       ` Nikolay Dimitrov
  0 siblings, 0 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 17:50 UTC (permalink / raw)
  To: Andreas Müller; +Cc: meta-freescale@yoctoproject.org

Hi Andreas,

On 11/13/2014 05:48 PM, Andreas Müller wrote:
> On Thu, Nov 13, 2014 at 4:17 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi Andreas,
>>
>>
>> On 11/13/2014 11:29 AM, Andreas Müller wrote:
>>>
>>> On Wed, Nov 12, 2014 at 11:58 PM, Nikolay Dimitrov <picmaster@mail.bg>
>>> wrote:
>>>>
>>>> Hi guys,
>>>>
>>>> I'm trying to use unmodified dizzy build with imx6q sabresd, for
>>>> testing video playback. U-Boot outputs HDMI image during boot, but in
>>>> Linux there's no HDMI image (no console, no video playback).
>>>>
>>>> The image is "fsl-image-multimedia-full", kernel 3.10.17. The device
>>>> files /dev/video* and /dev/fb* are available, but gstreamer playback
>>>> doesn't output any image on the HDMI port (seems to be stuck instead of
>>>> playing).
>>>>
>>>> The kernel cmdline doesn't specify any video settings, which typically
>>>> is an issue, but when I add the video bootargs:
>>>>
>>>> ...video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24...
>>>>
>>>> The board stops to print any boot messages after "Starting kernel..."
>>>> and seems to be stuck. Removing the video bootargs allows again to boot
>>>> normally.
>>>>
>>>> I must admit that I'm somewhat puzzled by this behavior, as I already
>>>> have daizy running with 3.10.17 on a custom board, and the video is
>>>> working there with almost the same bootargs. Do you guys have any ideas
>>>> for how to configure imx6q sabresd for HDMI video?
>>>>
>>>> Thanks in advance. Regards,
>>>> Nikolay
>>>> --
>>>
>>> Had same here.
>>>
>>> I think there are two problems:
>>> * 3.10.17 EDID decoding works only for monitors with EDID extended
>>> blocks (patch 0001..)
>>> * 1024x768 is not a CEA mode. If I read the code of 3.10.17 correct,
>>> HDMI supports only modes which are found in
>>> drivers/video/mxc/mxc_edid.c const struct fb_videomode
>>> mxc_cea_mode[64]. I hacked up working solution (patch 0002..). Note
>>> that this is just a hack - it might lead to incorrect colour space
>>> conversion or wrong PixelRepetitionOutput (see mxc_hdmi_setup:
>>> hdmi->vic is always 0 for my patches).
>>>
>>> These patches were tested with two monitors (1280x1024 / 1650x<I
>>> forgot>) and seem to work fine.
>>
>>
>> Thanks for your detailed answer. I remember seeing discussions on the
>> net about a safe fallback resolution for imx6 hdmi, so that's the only
>> reason to choose 1024x768.
>>
>> Also, are you sure that the HDMI code doesn't use the CVT (Common VESA
>> Table) resolutions? Need to check this. I'll also look a the code
>> which you pointed me to, and try your patches.
>>
>> I'm not looking for big or pixel-exact resolutions on HDMI, just some
>> reasonable resolution so I can test my gstreamer issues there :).
>>
>> Regards,
>> Nikolay
> After re reading this thread I saw that my patches are addressing a
> different problem. In short: Whatever monitor I connected to HDMI (via
> DVI) I got only 640x480 and complaints like
>
> [    0.829299] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
> [    0.960509] mxc_hdmi 20e0000.hdmi_video: Read EDID again
> [    0.960522] mxc_hdmi 20e0000.hdmi_video: mxc_edid_read_internal
> [    1.091703] mxc_hdmi 20e0000.hdmi_video: No modes read from edid
> [    1.091714] mxc_hdmi 20e0000.hdmi_video: create default modelist

Ahh, I see. Yes, I also think they are 2 separate issues. Still, thanks 
for trying to help.

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 17:46     ` Nikolay Dimitrov
@ 2014-11-13 19:34       ` Nikolay Dimitrov
  2014-11-13 20:50         ` Daiane Angolini
  2014-11-14 10:59         ` Nikolay Dimitrov
  0 siblings, 2 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 19:34 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

Hi guys,

Thanks to Fabio the HDMI is now working. Here's how:

1. Disabled HDMI support in u-boot-fsl (actually disabled all video-
related support, as it was easier/faster).
2. Added the usual video configuration to "mmcarg" env-var:

video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24

3. Booted the board (had to set mmcdev to 0 as I boot from SD2).
4. Observed that Xorg was running on the HDMI screen.
5. Played video via gstreamer and observed it's rendering on the screen
without issues.

After discussion with Andreas, I tested the following resolutions and
they worked OK:

- 640x480
- 800x600
- 1024x768
- 1280x720
(just don't have the time to test more as these were OK for my tests)

@Daiane: I checked the description for bug #6703, but I don't observe
the issue here. I left my HDMI cable connected all the time, and it
still works. I even power-cycled the board to make sure that the HDMI 
hardware is not left initialized from a previous boot. My understanding
is that the reason it works is Fabio's suggestion to disable U-Boot
HDMI support.

Thanks to everyone for the constructive discussion.

Kind regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 19:34       ` Nikolay Dimitrov
@ 2014-11-13 20:50         ` Daiane Angolini
  2014-11-13 22:22           ` Nikolay Dimitrov
  2014-11-14 10:59         ` Nikolay Dimitrov
  1 sibling, 1 reply; 17+ messages in thread
From: Daiane Angolini @ 2014-11-13 20:50 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

On Thu, Nov 13, 2014 at 5:34 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> Hi guys,
>
> Thanks to Fabio the HDMI is now working. Here's how:
>
> 1. Disabled HDMI support in u-boot-fsl (actually disabled all video-
> related support, as it was easier/faster).
> 2. Added the usual video configuration to "mmcarg" env-var:
>
> video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
>
> 3. Booted the board (had to set mmcdev to 0 as I boot from SD2).
> 4. Observed that Xorg was running on the HDMI screen.
> 5. Played video via gstreamer and observed it's rendering on the screen
> without issues.
>
> After discussion with Andreas, I tested the following resolutions and
> they worked OK:
>
> - 640x480
> - 800x600
> - 1024x768
> - 1280x720
> (just don't have the time to test more as these were OK for my tests)
>
> @Daiane: I checked the description for bug #6703, but I don't observe
> the issue here. I left my HDMI cable connected all the time, and it
> still works. I even power-cycled the board to make sure that the HDMI
> hardware is not left initialized from a previous boot. My understanding
> is that the reason it works is Fabio's suggestion to disable U-Boot
> HDMI support.

You are right, Nikolay, and if you see [1], the second comment, I
suggest turning of HDMI as a workaround, but using LVDS instead.

However, I got confused when you said you have never reproduced the
error regarding plug/unplug the cable.
Do you mean you was not able to reproduce it *after* get it fixed, or
you have never been able?

I would like to have you updating the bug with your workaround. Could
you, please leave a comment there with your how-to?

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6703#c2


Daiane
>
> Thanks to everyone for the constructive discussion.
>
> Kind regards,
> Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 20:50         ` Daiane Angolini
@ 2014-11-13 22:22           ` Nikolay Dimitrov
  2014-11-14  9:13             ` Daiane Angolini
  2014-11-14 10:36             ` Fabio Estevam
  0 siblings, 2 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-13 22:22 UTC (permalink / raw)
  To: Daiane Angolini; +Cc: meta-freescale@yoctoproject.org

Hi Daiane,

On 11/13/2014 10:50 PM, Daiane Angolini wrote:
> On Thu, Nov 13, 2014 at 5:34 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi guys,
>>
>> Thanks to Fabio the HDMI is now working. Here's how:
>>
>> 1. Disabled HDMI support in u-boot-fsl (actually disabled all video-
>> related support, as it was easier/faster).
>> 2. Added the usual video configuration to "mmcarg" env-var:
>>
>> video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
>>
>> 3. Booted the board (had to set mmcdev to 0 as I boot from SD2).
>> 4. Observed that Xorg was running on the HDMI screen.
>> 5. Played video via gstreamer and observed it's rendering on the screen
>> without issues.
>>
>> After discussion with Andreas, I tested the following resolutions and
>> they worked OK:
>>
>> - 640x480
>> - 800x600
>> - 1024x768
>> - 1280x720
>> (just don't have the time to test more as these were OK for my tests)
>>
>> @Daiane: I checked the description for bug #6703, but I don't observe
>> the issue here. I left my HDMI cable connected all the time, and it
>> still works. I even power-cycled the board to make sure that the HDMI
>> hardware is not left initialized from a previous boot. My understanding
>> is that the reason it works is Fabio's suggestion to disable U-Boot
>> HDMI support.
>
> You are right, Nikolay, and if you see [1], the second comment, I
> suggest turning of HDMI as a workaround, but using LVDS instead.
>
> However, I got confused when you said you have never reproduced the
> error regarding plug/unplug the cable.
> Do you mean you was not able to reproduce it *after* get it fixed, or
> you have never been able?

Sorry for the confusion. After I modified U-Boot, I didn't observed the
issue. Btw, after seeing your comment I went and reverted the change
just to be sure what's happening. And it turned out that you're right,
the issue can again be reproduced as described in #6703. Just to be
more clear, here's what I've tested:

1. Unmodified U-Boot, HDMI cable connected during power-on: kernel hangs
2. Unmodified U-Boot, HDMI cable connected later: works OK
3. Disabled U-Boot video, HDMI cable connected during power-on: works OK
4. Disabled U-Boot video, HDMI cable connected later: works OK

> I would like to have you updating the bug with your workaround. Could
> you, please leave a comment there with your how-to?

Sure, np.

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 22:22           ` Nikolay Dimitrov
@ 2014-11-14  9:13             ` Daiane Angolini
  2014-11-14 10:36             ` Fabio Estevam
  1 sibling, 0 replies; 17+ messages in thread
From: Daiane Angolini @ 2014-11-14  9:13 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

On Thu, Nov 13, 2014 at 8:22 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
> Hi Daiane,
>
>
> On 11/13/2014 10:50 PM, Daiane Angolini wrote:
>>
>> On Thu, Nov 13, 2014 at 5:34 PM, Nikolay Dimitrov <picmaster@mail.bg>
>> wrote:
>>>
>>> Hi guys,
>>>
>>> Thanks to Fabio the HDMI is now working. Here's how:
>>>
>>> 1. Disabled HDMI support in u-boot-fsl (actually disabled all video-
>>> related support, as it was easier/faster).
>>> 2. Added the usual video configuration to "mmcarg" env-var:
>>>
>>> video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
>>>
>>> 3. Booted the board (had to set mmcdev to 0 as I boot from SD2).
>>> 4. Observed that Xorg was running on the HDMI screen.
>>> 5. Played video via gstreamer and observed it's rendering on the screen
>>> without issues.
>>>
>>> After discussion with Andreas, I tested the following resolutions and
>>> they worked OK:
>>>
>>> - 640x480
>>> - 800x600
>>> - 1024x768
>>> - 1280x720
>>> (just don't have the time to test more as these were OK for my tests)
>>>
>>> @Daiane: I checked the description for bug #6703, but I don't observe
>>> the issue here. I left my HDMI cable connected all the time, and it
>>> still works. I even power-cycled the board to make sure that the HDMI
>>> hardware is not left initialized from a previous boot. My understanding
>>> is that the reason it works is Fabio's suggestion to disable U-Boot
>>> HDMI support.
>>
>>
>> You are right, Nikolay, and if you see [1], the second comment, I
>> suggest turning of HDMI as a workaround, but using LVDS instead.
>>
>> However, I got confused when you said you have never reproduced the
>> error regarding plug/unplug the cable.
>> Do you mean you was not able to reproduce it *after* get it fixed, or
>> you have never been able?
>
>
> Sorry for the confusion. After I modified U-Boot, I didn't observed the
> issue. Btw, after seeing your comment I went and reverted the change
> just to be sure what's happening. And it turned out that you're right,
> the issue can again be reproduced as described in #6703. Just to be
> more clear, here's what I've tested:
>
> 1. Unmodified U-Boot, HDMI cable connected during power-on: kernel hangs
> 2. Unmodified U-Boot, HDMI cable connected later: works OK
> 3. Disabled U-Boot video, HDMI cable connected during power-on: works OK
> 4. Disabled U-Boot video, HDMI cable connected later: works OK

Ok!
Great, and thanks ;-)

>
>> I would like to have you updating the bug with your workaround. Could
>> you, please leave a comment there with your how-to?
>
>
> Sure, np.

=D

Daiane
>
> Regards,
> Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 22:22           ` Nikolay Dimitrov
  2014-11-14  9:13             ` Daiane Angolini
@ 2014-11-14 10:36             ` Fabio Estevam
  2014-11-17  1:41               ` Nikolay Dimitrov
  1 sibling, 1 reply; 17+ messages in thread
From: Fabio Estevam @ 2014-11-14 10:36 UTC (permalink / raw)
  To: Nikolay Dimitrov; +Cc: meta-freescale@yoctoproject.org

Hi Nikolay,

On Thu, Nov 13, 2014 at 8:22 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:

> Sorry for the confusion. After I modified U-Boot, I didn't observed the
> issue. Btw, after seeing your comment I went and reverted the change
> just to be sure what's happening. And it turned out that you're right,
> the issue can again be reproduced as described in #6703. Just to be
> more clear, here's what I've tested:
>
> 1. Unmodified U-Boot, HDMI cable connected during power-on: kernel hangs
> 2. Unmodified U-Boot, HDMI cable connected later: works OK
> 3. Disabled U-Boot video, HDMI cable connected during power-on: works OK
> 4. Disabled U-Boot video, HDMI cable connected later: works OK

Does it work if you use the original U-boot and use the proposed fix
from this thread?
https://community.freescale.com/thread/327503

If so, could you please prepare a patch?

Thanks


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-13 19:34       ` Nikolay Dimitrov
  2014-11-13 20:50         ` Daiane Angolini
@ 2014-11-14 10:59         ` Nikolay Dimitrov
  1 sibling, 0 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-14 10:59 UTC (permalink / raw)
  To: meta-freescale

Hi everyone,

On 11/13/2014 09:34 PM, Nikolay Dimitrov wrote:
> 2. Added the usual video configuration to "mmcarg" env-var:

"mmcarg" should be actually "mmcargs". Sorry for the typo!

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: No HDMI video on imx6qsabresd with dizzy
  2014-11-14 10:36             ` Fabio Estevam
@ 2014-11-17  1:41               ` Nikolay Dimitrov
  0 siblings, 0 replies; 17+ messages in thread
From: Nikolay Dimitrov @ 2014-11-17  1:41 UTC (permalink / raw)
  To: Fabio Estevam; +Cc: meta-freescale@yoctoproject.org

Hi Fabio,

On 11/14/2014 12:36 PM, Fabio Estevam wrote:
> Hi Nikolay,
>
> On Thu, Nov 13, 2014 at 8:22 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>
>> Sorry for the confusion. After I modified U-Boot, I didn't observed the
>> issue. Btw, after seeing your comment I went and reverted the change
>> just to be sure what's happening. And it turned out that you're right,
>> the issue can again be reproduced as described in #6703. Just to be
>> more clear, here's what I've tested:
>>
>> 1. Unmodified U-Boot, HDMI cable connected during power-on: kernel hangs
>> 2. Unmodified U-Boot, HDMI cable connected later: works OK
>> 3. Disabled U-Boot video, HDMI cable connected during power-on: works OK
>> 4. Disabled U-Boot video, HDMI cable connected later: works OK
>
> Does it work if you use the original U-boot and use the proposed fix
> from this thread?
> https://community.freescale.com/thread/327503
>
> If so, could you please prepare a patch?
>
> Thanks

I haven't forgot this one, but will do it later, as I'm being pushed for 
high-priority issues at the moment.

Regards,
Nikolay


^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2014-11-17  1:41 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-12 22:58 No HDMI video on imx6qsabresd with dizzy Nikolay Dimitrov
2014-11-12 23:02 ` Fabio Estevam
2014-11-13 10:30   ` Daiane Angolini
2014-11-13 15:18     ` Nikolay Dimitrov
2014-11-13 15:10   ` Nikolay Dimitrov
2014-11-13 17:46     ` Nikolay Dimitrov
2014-11-13 19:34       ` Nikolay Dimitrov
2014-11-13 20:50         ` Daiane Angolini
2014-11-13 22:22           ` Nikolay Dimitrov
2014-11-14  9:13             ` Daiane Angolini
2014-11-14 10:36             ` Fabio Estevam
2014-11-17  1:41               ` Nikolay Dimitrov
2014-11-14 10:59         ` Nikolay Dimitrov
2014-11-13  9:29 ` Andreas Müller
2014-11-13 15:17   ` Nikolay Dimitrov
2014-11-13 15:48     ` Andreas Müller
2014-11-13 17:50       ` Nikolay Dimitrov

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.