All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Peter Bergin <peter.bergin@tritech.se>,
	 Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Troy <troy.kisky@boundarydevices.com>
Subject: Re: No HDMI signal from Nitrogen6x board with daisy
Date: Fri, 30 May 2014 18:54:30 -0700	[thread overview]
Message-ID: <53893656.10204@boundarydevices.com> (raw)
In-Reply-To: <43F0718C449F6A46B393DA2BEC8E01280C4F3864@post.tritech.se>

Hi Peter,

On 05/28/2014 09:09 AM, Peter Bergin wrote:
> Hi Eric,
>
> On 05/28/2014 04:03 PM, Eric Nelson wrote:
>> Thanks Peter,
>>
>> On 05/27/2014 11:51 PM, Peter Bergin wrote:
>>> Hi Eric,
>>>
>>> On 05/27/2014 11:11 PM, Eric Nelson wrote:
>>>> Hi Peter,
>>>>
>>>> On 05/25/2014 11:43 PM, Peter Bergin wrote:
>>>>> Hi Eric,
>>>>>
>>>>>    <snip>
>>>>>
>>>>> In order to understand more what happens during the process I have
>>>>> enabled dynamic debug in the kernel and turned on messages from mxc_hdmi
>>>>> and mxc_ipu. I have attached my /var/log/messages if someone more
>>>>> familiar with the drivers can have a look.
>>>>>
>>>> Thanks for the detailed information.
>>>>
>>>>> IPU_INT_STAT_5 is classed as Error Interrupts in the Reference Manual.
>>>>>
>>>>> May 26 06:02:30 nitrogen6x user.warn kernel: imx-ipuv3 2400000.ipu: IPU
>>>>> Warning - IPU_INT_STAT_5 = 0x00800000
>>>>>
>>>>> This seems to be a IMDAC_NFB4EOF_ERR_x. NFB4EOF - New-frame before
>>>>> end-of-frame.
>>>>>
>>>>> How can I get more understanding what's wrong in the IPU? Any ideas?
>>>>>
>>>> Nothing concrete. Perhaps the Freescaler's have some idea.
>>>>
>>>> The only time I've seen the NFB4EOF error has been when I've
>>>> had a bug (in a camera driver). I believe it means that there's
>>>> an initialization problem.
>>>>
>>>>
>>>> I've been trying to compare against what I see here,
>>>> and the two primary suspects are:
>>>>
>>>> 	- some quirk of your EDID
>>>> 	- the fact that you're running an older processor revision
>>>> 	(TO 1.0).
>>>>
>>>> I haven't yet found a TO 1.0 board to test against.


After trying everything else (hard-coding your EDID, and using a DVI
cable), I managed to find a board with Silicon Revision 1.0, and
it's failing more or less as you described:

	- 640x480 works
	- 1920x1080p fails

I also see those "timeout waiting for flip irq" messages whenever
switching to a resolution that doesn't function.

I'm not sure why, but it's probably time to grep through those pesky
tests for tapeout:
	imx_get_soc_revision() == IMX_CHIP_REVISION_1_0

TO 1.0 **did** work at 1080P in the older kernels.

Regards,


Eric


  reply	other threads:[~2014-05-31  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  7:23 No HDMI signal from Nitrogen6x board with daisy Peter Bergin
2014-05-23 12:16 ` Otavio Salvador
2014-05-24  0:18   ` Eric Nelson
2014-05-24  0:58     ` Eric Nelson
2014-05-24  1:23       ` Eric Nelson
2014-05-26  6:43         ` Peter Bergin
2014-05-27 21:11           ` Eric Nelson
2014-05-28  6:51             ` Peter Bergin
2014-05-28 14:02               ` Eric Nelson
2014-05-28 15:45                 ` Haakon Stende
2014-05-28 16:09                 ` Peter Bergin
2014-05-31  1:54                   ` Eric Nelson [this message]
2014-05-31 21:16                     ` Eric Nelson

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=53893656.10204@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=peter.bergin@tritech.se \
    --cc=troy.kisky@boundarydevices.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 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.