* No HDMI signal from Nitrogen6x board with daisy
@ 2014-05-23 7:23 Peter Bergin
2014-05-23 12:16 ` Otavio Salvador
0 siblings, 1 reply; 13+ messages in thread
From: Peter Bergin @ 2014-05-23 7:23 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
Hi,
I have trouble with my Nitrogen6x board after upgrade to daisy build. I can not get any HDMI signal out of the board after boot. During boot u-boot can show content on screen but when booted the monitor does not detect the signal.
I have updated to u-boot 2014.04. I have tried with the pre-built image found at Boundary Devices with same result as my own build.
I see this printout on the console after boot:
mxc_sdc_fb fb.27: timeout when waiting for flip irq
mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
mxc_sdc_fb fb.27: timeout when waiting for flip irq
mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
mxc_sdc_fb fb.27: timeout when waiting for flip irq
mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
I have also posted a, still unanswered, question on the Freescale community page (https://community.freescale.com/message/405002).
Any help is really appreciated! Any ideas?
Thanks,
/Peter
[cid:tritech-logo2405d1]
Peter Bergin
peter.bergin@tritech.se
+46 733 35 21 05
www.tritech.se<http://www.tritech.se>
+46 31 763 38 00
Nordstadstorget 6
SE-411 05 G?teborg, Sweden
[-- Attachment #1.2: Type: text/html, Size: 5969 bytes --]
[-- Attachment #2: tritech-logo2405d1 --]
[-- Type: image/jpeg, Size: 1536 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
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
0 siblings, 1 reply; 13+ messages in thread
From: Otavio Salvador @ 2014-05-23 12:16 UTC (permalink / raw)
To: Peter Bergin; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
On Fri, May 23, 2014 at 4:23 AM, Peter Bergin <peter.bergin@tritech.se>wrote:
> I have trouble with my Nitrogen6x board after upgrade to daisy build. I
> can not get any HDMI signal out of the board after boot. During boot u-boot
> can show content on screen but when booted the monitor does not detect the
> signal.
>
> I have updated to u-boot 2014.04. I have tried with the pre-built image
> found at Boundary Devices with same result as my own build.
>
> I see this printout on the console after boot:
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
>
> I have also posted a, still unanswered, question on the Freescale
> community page (https://community.freescale.com/message/405002).
>
> Any help is really appreciated! Any ideas?
>
I think it might be your monitor do not support the frequency it is using.
I am adding Eric in Cc so he can comment on this.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
[-- Attachment #2: Type: text/html, Size: 4375 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-23 12:16 ` Otavio Salvador
@ 2014-05-24 0:18 ` Eric Nelson
2014-05-24 0:58 ` Eric Nelson
0 siblings, 1 reply; 13+ messages in thread
From: Eric Nelson @ 2014-05-24 0:18 UTC (permalink / raw)
To: Otavio Salvador, Peter Bergin; +Cc: meta-freescale@yoctoproject.org
Hello Peter,
On 05/23/2014 05:16 AM, Otavio Salvador wrote:
>
> On Fri, May 23, 2014 at 4:23 AM, Peter Bergin <peter.bergin@tritech.se
> <mailto:peter.bergin@tritech.se>> wrote:
>
> I have trouble with my Nitrogen6x board after upgrade to daisy
> build. I can not get any HDMI signal out of the board after boot.
> During boot u-boot can show content on screen but when booted the
> monitor does not detect the signal.
>
> I have updated to u-boot 2014.04. I have tried with the pre-built
> image found at Boundary Devices with same result as my own build.
>
This is not likely to be a U-Boot level thing.
> I see this printout on the console after boot:
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
> mxc_sdc_fb fb.27: timeout when waiting for flip irq
> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
>
> I have also posted a, still unanswered, question on the Freescale
> community page (https://community.freescale.com/message/405002).
>
I saw that post, but have been struggling to find time to reproduce it.
A nominal build of Daisy/fsl-image-machine-test just seemed to
work for me at 1080P60.
Are you also running 1080P (i.e. with a custom boot script)?
Can you forward the content of /proc/cmdline?
> Any help is really appreciated! Any ideas?
>
> I think it might be your monitor do not support the frequency it is using.
>
If your monitor supports EDID, you should be able to tell by
looking in sysfs:
# cat /sys/class/graphics/fb0/mode
... currently negotiated mode here
# cat /sys/class/graphics/fb0/modes
... list of supported modes should be here
> I am adding Eric in Cc so he can comment on this.
>
I'm afraid I have more questions than advice.
Can you tell me more about what image you're running? Is it based
on X, DFB, Wayland?
Do you see the penguins during Linux boot?
Please advise,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-24 0:18 ` Eric Nelson
@ 2014-05-24 0:58 ` Eric Nelson
2014-05-24 1:23 ` Eric Nelson
0 siblings, 1 reply; 13+ messages in thread
From: Eric Nelson @ 2014-05-24 0:58 UTC (permalink / raw)
To: Otavio Salvador, Peter Bergin; +Cc: meta-freescale@yoctoproject.org, Troy
Sorry Peter,
I didn't recall that the other post was from you, so some
of these questions are answered.
On 05/23/2014 05:18 PM, Eric Nelson wrote:
> Hello Peter,
>
> On 05/23/2014 05:16 AM, Otavio Salvador wrote:
>>
>> On Fri, May 23, 2014 at 4:23 AM, Peter Bergin <peter.bergin@tritech.se
>> <mailto:peter.bergin@tritech.se>> wrote:
>>
>> I have trouble with my Nitrogen6x board after upgrade to daisy
>> build. I can not get any HDMI signal out of the board after boot.
>> During boot u-boot can show content on screen but when booted the
>> monitor does not detect the signal.
>>
>> I have updated to u-boot 2014.04. I have tried with the pre-built
>> image found at Boundary Devices with same result as my own build.
>>
>
> This is not likely to be a U-Boot level thing.
>
>> I see this printout on the console after boot:
>> mxc_sdc_fb fb.27: timeout when waiting for flip irq
>> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
>> mxc_sdc_fb fb.27: timeout when waiting for flip irq
>> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
>> mxc_sdc_fb fb.27: timeout when waiting for flip irq
>> mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
>>
>> I have also posted a, still unanswered, question on the Freescale
>> community page (https://community.freescale.com/message/405002).
>>
>
> I saw that post, but have been struggling to find time to reproduce it.
> A nominal build of Daisy/fsl-image-machine-test just seemed to
> work for me at 1080P60.
>
> Are you also running 1080P (i.e. with a custom boot script)?
>
> Can you forward the content of /proc/cmdline?
>
Got it:
enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait
root=/dev/mmcblk0p2
This looks reasonable.
>> Any help is really appreciated! Any ideas?
>>
>> I think it might be your monitor do not support the frequency it is
>> using.
>>
> If your monitor supports EDID, you should be able to tell by
> looking in sysfs:
>
> # cat /sys/class/graphics/fb0/mode
> ... currently negotiated mode here
>
> # cat /sys/class/graphics/fb0/modes
> ... list of supported modes should be here
>
I see in your post that you decoded the EDID information
in U-Boot, and it certainly says that your monitor supports
1080P60:
1920x1080 60 Hz (detailed)
In the serial output, I also see 720P come up before
before a transition to 1080P.
imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000
mxc_sdc_fb fb.25: 1280x720 h_sync,r,l: 40,110,220 v_sync,l,u: 5,5,20
pixclock=74250000 Hz
...
mxc_sdc_fb fb.25: 1920x1080 h_sync,r,l: 44,528,148 v_sync,l,u: 5,4,36
pixclock=148500000 Hz
imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000
I suspect that this is the source of the issue, because your monitor
doesn't appear to support 720P, but I'm not sure.
Hmmm. While testing your command-line, I'm seeing some weirdness too.
With your arguments, my display gets confgured as 1024x768.
If I add the "mxc_hdmi.only_cea=1" as is done in the boot script,
I get proper negotiation.
Can you try running this by hand?
U-Boot > setenv bootargs enable_wait_mode=off
video=mxcfb0:dev=hdmi,1920x1080MR@60,if=RGB24 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2 mxc_hdmi.only_cea=1
U-Boot > mmc dev 0 && fatload mmc 0 10800000 uImage && bootm 10800000
I suspect we introduced a bug when pulling our "only_cea" patch
over to 3.10.17.
Please advise,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-24 0:58 ` Eric Nelson
@ 2014-05-24 1:23 ` Eric Nelson
2014-05-26 6:43 ` Peter Bergin
0 siblings, 1 reply; 13+ messages in thread
From: Eric Nelson @ 2014-05-24 1:23 UTC (permalink / raw)
To: Otavio Salvador, Peter Bergin; +Cc: meta-freescale@yoctoproject.org, Troy
On 05/23/2014 05:58 PM, Eric Nelson wrote:
> Sorry Peter,
>
> <snip>
>
> Can you try running this by hand?
>
> U-Boot > setenv bootargs enable_wait_mode=off
> video=mxcfb0:dev=hdmi,1920x1080MR@60,if=RGB24 video=mxcfb1:off
> video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
> vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
> mxc_hdmi.only_cea=1
> U-Boot > mmc dev 0 && fatload mmc 0 10800000 uImage && bootm 10800000
>
> I suspect we introduced a bug when pulling our "only_cea" patch
> over to 3.10.17.
>
Sorry about that. I pasted the 3.0.35 kernel parameters and
load commands.
Testing on the same version as you are, I found the same thing
though.
U-Boot > setenv bootargs enable_wait_mode=off
video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
U-Boot > mmc dev 0 && \
fatload mmc 0 10800000 uImage && \
fatload mmc 0 12000000 imx6q-nitrogen6x.dtb && \
bootm 10800000 - 12000000
Using the clause 'mxc_hdmi.only_cea=1' yields 1080P.
Without it, I get 1024x768.
So the bug is general and not specific to 3.10.17...
It's still not clear why you're getting no display at all
though, or where those IPU_INT_STAT_x or "timeout waiting
for flip irq" messages are coming from.
Can you try out the commands above?
Please advise,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-24 1:23 ` Eric Nelson
@ 2014-05-26 6:43 ` Peter Bergin
2014-05-27 21:11 ` Eric Nelson
0 siblings, 1 reply; 13+ messages in thread
From: Peter Bergin @ 2014-05-26 6:43 UTC (permalink / raw)
To: Eric Nelson, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]
Hi Eric,
On 05/24/2014 03:23 AM, Eric Nelson wrote:
> On 05/23/2014 05:58 PM, Eric Nelson wrote:
>> Sorry Peter,
>>
> > <snip>
> >
>> Can you try running this by hand?
>>
>> U-Boot > setenv bootargs enable_wait_mode=off
>> video=mxcfb0:dev=hdmi,1920x1080MR@60,if=RGB24 video=mxcfb1:off
>> video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
>> vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
>> mxc_hdmi.only_cea=1
>> U-Boot > mmc dev 0 && fatload mmc 0 10800000 uImage && bootm 10800000
>>
>> I suspect we introduced a bug when pulling our "only_cea" patch
>> over to 3.10.17.
>>
> Sorry about that. I pasted the 3.0.35 kernel parameters and
> load commands.
>
> Testing on the same version as you are, I found the same thing
> though.
>
> U-Boot > setenv bootargs enable_wait_mode=off
> video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off
> video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
> vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
> U-Boot > mmc dev 0 && \
> fatload mmc 0 10800000 uImage && \
> fatload mmc 0 12000000 imx6q-nitrogen6x.dtb && \
> bootm 10800000 - 12000000
>
> Using the clause 'mxc_hdmi.only_cea=1' yields 1080P.
> Without it, I get 1024x768.
> So the bug is general and not specific to 3.10.17...
>
> It's still not clear why you're getting no display at all
> though, or where those IPU_INT_STAT_x or "timeout waiting
> for flip irq" messages are coming from.
>
> Can you try out the commands above?
I have tried this on my board but get exactly the same behavior and
still no signal on HDMI.
>
> Please advise,
>
>
> Eric
>
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.
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?
I have also checked /sys/class/graphics/fb0 and made some tests.
root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
D:1920x1080p-60
root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
D:720x480p-59
D:720x576p-50
D:1280x720p-50
D:1280x720p-60
D:1920x1080p-50
V:640x480p-60
D:1920x1080p-60
V:640x480p-60
I have tried to set all of the above listed resolutions in modes. The
only resolution that works is V:640x480p-60. With this resolution set I
get signal on HDMI and the display shows my screen.
Regards,
/Peter
[-- Attachment #2: messages --]
[-- Type: text/plain, Size: 86754 bytes --]
May 26 06:02:30 nitrogen6x syslog.info syslogd started: BusyBox v1.22.1
May 26 06:02:30 nitrogen6x user.notice kernel: klogd started: BusyBox v1.22.1 (2014-05-15 00:37:47 CEST)
May 26 06:02:30 nitrogen6x user.info kernel: Booting Linux on physical CPU 0x0
May 26 06:02:30 nitrogen6x user.notice kernel: Linux version 3.10.17-1.0.0_ga+yocto+g731f96d (petber@petber-linux-laptop) (gcc version 4.8.2 (GCC) ) #3 SMP Fri May 23 15:42:46 CEST 2014
May 26 06:02:30 nitrogen6x user.warn kernel: CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
May 26 06:02:30 nitrogen6x user.warn kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
May 26 06:02:30 nitrogen6x user.info kernel: Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Freescale i.MX6 Quad Nitrogen6x Board
May 26 06:02:30 nitrogen6x user.info kernel: cma: CMA: reserved 256 MiB at 40000000
May 26 06:02:30 nitrogen6x user.warn kernel: Memory policy: ECC disabled, Data cache writealloc
May 26 06:02:30 nitrogen6x user.debug kernel: On node 0 totalpages: 262144
May 26 06:02:30 nitrogen6x user.debug kernel: free_area_init_node: node 0, pgdat 8084b180, node_mem_map 808ba000
May 26 06:02:30 nitrogen6x user.debug kernel: DMA zone: 2048 pages used for memmap
May 26 06:02:30 nitrogen6x user.debug kernel: DMA zone: 0 pages reserved
May 26 06:02:30 nitrogen6x user.debug kernel: DMA zone: 262144 pages, LIFO batch:31
May 26 06:02:30 nitrogen6x user.info kernel: PERCPU: Embedded 8 pages/cpu @810d1000 s8704 r8192 d15872 u32768
May 26 06:02:30 nitrogen6x user.debug kernel: pcpu-alloc: s8704 r8192 d15872 u32768 alloc=8*4096
May 26 06:02:30 nitrogen6x user.debug kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
May 26 06:02:30 nitrogen6x user.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096
May 26 06:02:30 nitrogen6x user.notice kernel: Kernel command line: enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M dyndbg="module mxc_hdmi +pf;module mxc_hdmi_core +pf;module mxc_ipu +pf" consol
May 26 06:02:30 nitrogen6x user.info kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: Memory: 1024MB = 1024MB total
May 26 06:02:30 nitrogen6x user.notice kernel: Memory: 767720k/767720k available, 280856k reserved, 0K highmem
May 26 06:02:30 nitrogen6x user.notice kernel: Virtual kernel memory layout:
May 26 06:02:30 nitrogen6x user.notice kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
May 26 06:02:30 nitrogen6x user.notice kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
May 26 06:02:30 nitrogen6x user.notice kernel: vmalloc : 0xc0800000 - 0xff000000 (1000 MB)
May 26 06:02:30 nitrogen6x user.notice kernel: lowmem : 0x80000000 - 0xc0000000 (1024 MB)
May 26 06:02:30 nitrogen6x user.notice kernel: modules : 0x7f000000 - 0x80000000 ( 16 MB)
May 26 06:02:30 nitrogen6x user.notice kernel: .text : 0x80008000 - 0x807ccf9c (7956 kB)
May 26 06:02:30 nitrogen6x user.notice kernel: .init : 0x807cd000 - 0x80813200 ( 281 kB)
May 26 06:02:30 nitrogen6x user.notice kernel: .data : 0x80814000 - 0x80859ac0 ( 279 kB)
May 26 06:02:30 nitrogen6x user.notice kernel: .bss : 0x80859ac0 - 0x808b973c ( 384 kB)
May 26 06:02:30 nitrogen6x user.info kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
May 26 06:02:30 nitrogen6x user.info kernel: Hierarchical RCU implementation.
May 26 06:02:30 nitrogen6x user.info kernel: NR_IRQS:16 nr_irqs:16 16
May 26 06:02:30 nitrogen6x user.info kernel: L310 cache controller enabled
May 26 06:02:30 nitrogen6x user.info kernel: l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1048576 B
May 26 06:02:30 nitrogen6x user.info kernel: sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 65075ms
May 26 06:02:30 nitrogen6x user.info kernel: CPU identified as i.MX6Q, silicon rev 1.0
May 26 06:02:30 nitrogen6x user.info kernel: Console: colour dummy device 80x30
May 26 06:02:30 nitrogen6x user.info kernel: Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
May 26 06:02:30 nitrogen6x user.info kernel: pid_max: default: 32768 minimum: 301
May 26 06:02:30 nitrogen6x user.info kernel: Mount-cache hash table entries: 512
May 26 06:02:30 nitrogen6x user.info kernel: CPU: Testing write buffer coherency: ok
May 26 06:02:30 nitrogen6x user.info kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
May 26 06:02:30 nitrogen6x user.info kernel: Setting up static identity map for 0x805eac70 - 0x805eacc8
May 26 06:02:30 nitrogen6x user.warn kernel: CPU1: Booted secondary processor
May 26 06:02:30 nitrogen6x user.info kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
May 26 06:02:30 nitrogen6x user.warn kernel: CPU2: Booted secondary processor
May 26 06:02:30 nitrogen6x user.info kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
May 26 06:02:30 nitrogen6x user.warn kernel: CPU3: Booted secondary processor
May 26 06:02:30 nitrogen6x user.info kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
May 26 06:02:30 nitrogen6x user.info kernel: Brought up 4 CPUs
May 26 06:02:30 nitrogen6x user.info kernel: SMP: Total of 4 processors activated (6324.22 BogoMIPS).
May 26 06:02:30 nitrogen6x user.info kernel: CPU: All CPU(s) started in SVC mode.
May 26 06:02:30 nitrogen6x user.info kernel: devtmpfs: initialized
May 26 06:02:30 nitrogen6x user.info kernel: pinctrl core: initialized pinctrl subsystem
May 26 06:02:30 nitrogen6x user.info kernel: regulator-dummy: no parameters
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 16
May 26 06:02:30 nitrogen6x user.info kernel: DMA: preallocated 256 KiB pool for atomic coherent allocations
May 26 06:02:30 nitrogen6x user.info kernel: Use WDOG1 as reset source
May 26 06:02:30 nitrogen6x user.info kernel: syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered
May 26 06:02:30 nitrogen6x user.info kernel: vdd1p1: 800 <--> 1375 mV at 1125 mV
May 26 06:02:30 nitrogen6x user.info kernel: vdd3p0: 2800 <--> 3150 mV at 3000 mV
May 26 06:02:30 nitrogen6x user.info kernel: vdd2p5: 2000 <--> 2750 mV at 2425 mV
May 26 06:02:30 nitrogen6x user.info kernel: cpu: 725 <--> 1450 mV at 1100 mV
May 26 06:02:30 nitrogen6x user.info kernel: vddpu: 725 <--> 1450 mV at 1100 mV
May 26 06:02:30 nitrogen6x user.info kernel: vddsoc: 725 <--> 1450 mV at 1175 mV
May 26 06:02:30 nitrogen6x user.info kernel: syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered
May 26 06:02:30 nitrogen6x user.info kernel: syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered
May 26 06:02:30 nitrogen6x user.info kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
May 26 06:02:30 nitrogen6x user.info kernel: hw-breakpoint: maximum watchpoint size is 4 bytes.
May 26 06:02:30 nitrogen6x user.info kernel: imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
May 26 06:02:30 nitrogen6x user.info kernel: bio: create slab <bio-0> at 0
May 26 06:02:30 nitrogen6x user.info kernel: 1P8V: 1800 mV
May 26 06:02:30 nitrogen6x user.info kernel: 2P5V: 2500 mV
May 26 06:02:30 nitrogen6x user.info kernel: 3P3V: 3300 mV
May 26 06:02:30 nitrogen6x user.info kernel: usb_otg_vbus: 5000 mV
May 26 06:02:30 nitrogen6x user.info kernel: wilink_wl_en: 1800 mV
May 26 06:02:30 nitrogen6x user.info kernel: vgaarb: loaded
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_core_probe: mxc_hdmi_core_probe isfr_clk:540000000
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_core_probe:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_core_probe hdmi hw base = 0x00120000
May 26 06:02:30 nitrogen6x user.notice kernel: SCSI subsystem initialized
May 26 06:02:30 nitrogen6x user.debug kernel: libata version 3.00 loaded.
May 26 06:02:30 nitrogen6x user.info kernel: usbcore: registered new interface driver usbfs
May 26 06:02:30 nitrogen6x user.info kernel: usbcore: registered new interface driver hub
May 26 06:02:30 nitrogen6x user.info kernel: usbcore: registered new device driver usb
May 26 06:02:30 nitrogen6x user.info kernel: i2c i2c-0: IMX I2C adapter registered
May 26 06:02:30 nitrogen6x user.info kernel: i2c i2c-1: IMX I2C adapter registered
May 26 06:02:30 nitrogen6x user.info kernel: i2c i2c-2: IMX I2C adapter registered
May 26 06:02:30 nitrogen6x user.info kernel: Linux video capture interface: v2.00
May 26 06:02:30 nitrogen6x user.info kernel: pps_core: LinuxPPS API ver. 1 registered
May 26 06:02:30 nitrogen6x user.info kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
May 26 06:02:30 nitrogen6x user.info kernel: PTP clock support registered
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: <ipu_probe>
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU rev:4
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU CM Regs = c0816000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU IC Regs = c081e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU IDMAC Regs = c0826000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DP Regs = c082e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DC Regs = c0836000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DMFC Regs = c083e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DI0 Regs = c0846000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DI1 Regs = c084e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU SMFC Regs = c0856000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU CSI0 Regs = c085e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU CSI1 Regs = c086a000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU CPMem = c0900000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU TPMem = c08e0000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU DC Template Mem = c0940000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU Display Region 1 Mem = c086e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2400000.ipu: IPU VDI Regs = c086c000
May 26 06:02:30 nitrogen6x user.info kernel: imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_clk_setup_enable: imx-ipuv3 2400000.ipu: ipu_clk = 264000000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:0, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di1 read BS_CLKGEN0 div:0, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_task_thread: ipu_task_thread: sched_setaffinity cpu:0.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_task_thread: ipu_task_thread: sched_setaffinity cpu:0.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: <ipu_probe>
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU rev:4
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU CM Regs = c0876000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU IC Regs = c087e000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU IDMAC Regs = c08be000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DP Regs = c08c6000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DC Regs = c08c8000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DMFC Regs = c08ca000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DI0 Regs = c08cc000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DI1 Regs = c08ce000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU SMFC Regs = c08d0000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU CSI0 Regs = c08d2000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU CSI1 Regs = c08d4000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU CPMem = c0980000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU TPMem = c09c0000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU DC Template Mem = c0a00000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU Display Region 1 Mem = c08d8000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_probe: imx-ipuv3 2800000.ipu: IPU VDI Regs = c08d6000
May 26 06:02:30 nitrogen6x user.info kernel: imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_clk_setup_enable: imx-ipuv3 2800000.ipu: ipu_clk = 264000000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:0, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di1 read BS_CLKGEN0 div:0, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_task_thread: ipu_task_thread: sched_setaffinity cpu:0.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_task_thread: ipu_task_thread: sched_setaffinity cpu:0.
May 26 06:02:30 nitrogen6x user.info kernel: mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed ipu0 csi1
May 26 06:02:30 nitrogen6x user.info kernel: mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a
May 26 06:02:30 nitrogen6x user.info kernel: MIPI CSI2 driver module loaded
May 26 06:02:30 nitrogen6x user.info kernel: Advanced Linux Sound Architecture Driver Initialized.
May 26 06:02:30 nitrogen6x user.info kernel: Switching to clocksource mxc_timer1
May 26 06:02:30 nitrogen6x user.err kernel: imx6q-pcie 1ffc000.pcie: phy link never came up
May 26 06:02:30 nitrogen6x user.info kernel: PCI host bridge to bus 0000:00
May 26 06:02:30 nitrogen6x user.info kernel: pci_bus 0000:00: root bus resource [io 0x1000-0x10000]
May 26 06:02:30 nitrogen6x user.info kernel: pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
May 26 06:02:30 nitrogen6x user.info kernel: pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
May 26 06:02:30 nitrogen6x user.debug kernel: pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
May 26 06:02:30 nitrogen6x user.debug kernel: pci 0000:00:00.0: reg 10: [mem 0x00000000-0x000fffff]
May 26 06:02:30 nitrogen6x user.debug kernel: pci 0000:00:00.0: reg 38: [mem 0x00000000-0x0000ffff pref]
May 26 06:02:30 nitrogen6x user.debug kernel: pci 0000:00:00.0: supports D1
May 26 06:02:30 nitrogen6x user.debug kernel: pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
May 26 06:02:30 nitrogen6x user.info kernel: PCI: bus0: Fast back to back transfers disabled
May 26 06:02:30 nitrogen6x user.info kernel: PCI: bus1: Fast back to back transfers enabled
May 26 06:02:30 nitrogen6x user.debug kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
May 26 06:02:30 nitrogen6x user.debug kernel: pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
May 26 06:02:30 nitrogen6x user.info kernel: pci 0000:00:00.0: BAR 0: assigned [mem 0x01000000-0x010fffff]
May 26 06:02:30 nitrogen6x user.info kernel: pci 0000:00:00.0: BAR 6: assigned [mem 0x01100000-0x0110ffff pref]
May 26 06:02:30 nitrogen6x user.info kernel: pci 0000:00:00.0: PCI bridge to [bus 01]
May 26 06:02:30 nitrogen6x user.debug kernel: pci_bus 0000:00: resource 4 [io 0x1000-0x10000]
May 26 06:02:30 nitrogen6x user.debug kernel: pci_bus 0000:00: resource 5 [mem 0x01000000-0x01efffff]
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 2
May 26 06:02:30 nitrogen6x user.info kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: TCP: Hash tables configured (established 8192 bind 8192)
May 26 06:02:30 nitrogen6x user.info kernel: TCP: reno registered
May 26 06:02:30 nitrogen6x user.info kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 1
May 26 06:02:30 nitrogen6x user.info kernel: RPC: Registered named UNIX socket transport module.
May 26 06:02:30 nitrogen6x user.info kernel: RPC: Registered udp transport module.
May 26 06:02:30 nitrogen6x user.info kernel: RPC: Registered tcp transport module.
May 26 06:02:30 nitrogen6x user.info kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
May 26 06:02:30 nitrogen6x user.debug kernel: PCI: CLS 64 bytes, default 64
May 26 06:02:30 nitrogen6x user.info kernel: hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
May 26 06:02:30 nitrogen6x user.info kernel: pureg-dummy: no parameters
May 26 06:02:30 nitrogen6x user.info kernel: imx6_busfreq busfreq.15: DDR medium rate not supported.
May 26 06:02:30 nitrogen6x user.info kernel: Bus freq driver module loaded
May 26 06:02:30 nitrogen6x user.notice kernel: VFS: Disk quotas dquot_6.5.2
May 26 06:02:30 nitrogen6x user.warn kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
May 26 06:02:30 nitrogen6x user.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
May 26 06:02:30 nitrogen6x user.notice kernel: NFS: Registering the id_resolver key type
May 26 06:02:30 nitrogen6x user.notice kernel: Key type id_resolver registered
May 26 06:02:30 nitrogen6x user.notice kernel: Key type id_legacy registered
May 26 06:02:30 nitrogen6x user.info kernel: jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
May 26 06:02:30 nitrogen6x user.info kernel: fuse init (API version 7.22)
May 26 06:02:30 nitrogen6x user.info kernel: msgmni has been set to 2011
May 26 06:02:30 nitrogen6x user.info kernel: io scheduler noop registered
May 26 06:02:30 nitrogen6x user.info kernel: io scheduler deadline registered
May 26 06:02:30 nitrogen6x user.info kernel: io scheduler cfq registered (default)
May 26 06:02:30 nitrogen6x user.info kernel: imx-weim 21b8000.weim: WEIM driver registered.
May 26 06:02:30 nitrogen6x user.info kernel: i.MX PCIE endpoint device driver, version 0.1
May 26 06:02:30 nitrogen6x user.info kernel: MIPI DSI driver module loaded
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_hdcp_get_property: mxc_hdmi 20e0000.hdmi_video: hdcp disable
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: register mxc display driver hdmi
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_disp_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_disp_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init - default mode 1920x1080M@60 bpp=16
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_disp_init: mxc_hdmi 20e0000.hdmi_video: Enabled HDMI clocks
May 26 06:02:30 nitrogen6x user.info kernel: mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_set_clk_regenerator: hdmi_set_clk_regenerator: samplerate=48000 ratio=100 pixelclk=74250000 N=6144 cts=74250
May 26 06:02:30 nitrogen6x user.info kernel: fbcvt: 1920x1080@60: CVT Name - 2.073M9
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_disp_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init exit
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: Channel already disabled 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: Channel already uninitialized 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300000.
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:0, final_rate:2376000000, prate:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:30 nitrogen6x user.info kernel: imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 0010DCEF
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 08020000 01004000 00E7C000 F2C3BFC0 00082CA0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 1919,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 1079,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 3839
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_BLANK - UNBLANK
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_dp_dc_disable: imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_suspend: imx-ipuv3 2400000.ipu: ipu busfreq high release.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300006.
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_dmfc_init: imx-ipuv3 2400000.ipu: DMFC high resolution has set, will not change
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 0010DCEF
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 08020000 01004000 00E7C000 F2C3BFC0 00082CA0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 1919,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 1079,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 3839
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.warn kernel: imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000
May 26 06:02:30 nitrogen6x user.info kernel: Console: switching to colour frame buffer device 240x67
May 26 06:02:30 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_FB_REGISTERED
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_registered: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_fb_registered
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_hotplug: mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_hotplug: mxc_hdmi 20e0000.hdmi_video: Hotplug interrupt received
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 175110143
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: Channel already disabled 10
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: Channel already uninitialized 10
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.28: mxcfb1 is turned off!
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.29: mxcfb2 is turned off!
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.30: mxcfb3 is turned off!
May 26 06:02:30 nitrogen6x user.warn kernel: imx-sdma 20ec000.sdma: no iram assigned, using external mem
May 26 06:02:30 nitrogen6x user.info kernel: imx-sdma 20ec000.sdma: loaded firmware 1.1
May 26 06:02:30 nitrogen6x user.info kernel: imx-sdma 20ec000.sdma: initialized
May 26 06:02:30 nitrogen6x user.info kernel: Serial: IMX driver
May 26 06:02:30 nitrogen6x user.info kernel: 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
May 26 06:02:30 nitrogen6x user.info kernel: 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
May 26 06:02:30 nitrogen6x user.info kernel: console [ttymxc1] enabled
May 26 06:02:30 nitrogen6x user.debug kernel: hotplug_worker: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_stat0=0xf3, hdmi_phy_pol0=0xf2
May 26 06:02:30 nitrogen6x user.debug kernel: hotplug_worker: mxc_hdmi 20e0000.hdmi_video: EVENT=plugin
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_cable_connected: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_cable_connected
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_read_edid: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_read_edid
May 26 06:02:30 nitrogen6x user.info kernel: 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
May 26 06:02:30 nitrogen6x user.info kernel: serial: Freescale lpuart driver
May 26 06:02:30 nitrogen6x user.info kernel: [drm] Initialized drm 1.1.0 20060810
May 26 06:02:30 nitrogen6x user.info kernel: [drm] Initialized vivante 1.0.0 20120216 on minor 0
May 26 06:02:30 nitrogen6x user.info kernel: brd: module loaded
May 26 06:02:30 nitrogen6x user.info kernel: loop: module loaded
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_edid_rebuild_modelist
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 0:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 60, vmode = 0, flag = 17
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 2:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 640, yres = 480, freq = 60, vmode = 0, flag = 4
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 24:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 50, vmode = 32, flag = 1
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 25:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 1280, yres = 720, freq = 60, vmode = 32, flag = 1
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 26:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 1280, yres = 720, freq = 50, vmode = 32, flag = 1
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 27:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 720, yres = 576, freq = 50, vmode = 32, flag = 1
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: Added mode 28:
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_edid_rebuild_modelist: mxc_hdmi 20e0000.hdmi_video: xres = 720, yres = 480, freq = 59, vmode = 32, flag = 1
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_set_mode: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_set_mode: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode: New video mode
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_set_mode_to_vga_dvi: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode_to_vga_dvi
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_disable_overflow_interrupts: hdmi_disable_overflow_interrupts
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_notify_fb: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_disable: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.err kernel: Wait for CR ACK error!
May 26 06:02:30 nitrogen6x user.info kernel: sata phy RX_PLL is stable!
May 26 06:02:30 nitrogen6x user.info kernel: ahci: SSS flag set, parallel bus scan disabled
May 26 06:02:30 nitrogen6x user.info kernel: ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
May 26 06:02:30 nitrogen6x user.info kernel: ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst
May 26 06:02:30 nitrogen6x user.info kernel: scsi0 : ahci_platform
May 26 06:02:30 nitrogen6x user.info kernel: ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71
May 26 06:02:30 nitrogen6x user.info kernel: m25p80 spi32766.0: sst25vf016b (2048 Kbytes)
May 26 06:02:30 nitrogen6x user.notice kernel: 3 ofpart partitions found on MTD device spi32766.0
May 26 06:02:30 nitrogen6x user.notice kernel: Creating 3 MTD partitions on "spi32766.0":
May 26 06:02:30 nitrogen6x user.notice kernel: 0x000000000000-0x0000000c0000 : "U-Boot"
May 26 06:02:30 nitrogen6x user.notice kernel: 0x0000000c0000-0x0000000c2000 : "env"
May 26 06:02:30 nitrogen6x user.notice kernel: 0x0000000c2000-0x000000200000 : "Kernel"
May 26 06:02:30 nitrogen6x user.info kernel: spi_imx 2008000.ecspi: probed
May 26 06:02:30 nitrogen6x user.info kernel: phyirq=188
May 26 06:02:30 nitrogen6x user.info kernel: libphy: fec_enet_mii_bus: probed
May 26 06:02:30 nitrogen6x user.info kernel: fec 2188000.ethernet eth0: registered PHC device 0
May 26 06:02:30 nitrogen6x user.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
May 26 06:02:30 nitrogen6x user.info kernel: ehci-pci: EHCI PCI platform driver
May 26 06:02:30 nitrogen6x user.info kernel: usbcore: registered new interface driver usb-storage
May 26 06:02:30 nitrogen6x user.info kernel: setup_reset_gpio:-2
May 26 06:02:30 nitrogen6x user.info kernel: setup_reset_gpio:-2
May 26 06:02:30 nitrogen6x user.info kernel: ci_hdrc ci_hdrc.1: doesn't support gadget
May 26 06:02:30 nitrogen6x user.info kernel: ci_hdrc ci_hdrc.1: EHCI Host Controller
May 26 06:02:30 nitrogen6x user.info kernel: ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
May 26 06:02:30 nitrogen6x user.info kernel: ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
May 26 06:02:30 nitrogen6x user.info kernel: hub 1-0:1.0: USB hub found
May 26 06:02:30 nitrogen6x user.info kernel: hub 1-0:1.0: 1 port detected
May 26 06:02:30 nitrogen6x user.info kernel: mousedev: PS/2 mouse device common for all mice
May 26 06:02:30 nitrogen6x user.err kernel: egalax_ts 2-0004: Failed to read firmware version
May 26 06:02:30 nitrogen6x user.warn kernel: egalax_ts: probe of 2-0004 failed with error -5
May 26 06:02:30 nitrogen6x user.err kernel: ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
May 26 06:02:30 nitrogen6x user.info kernel: ft5x06: May 22 2014
May 26 06:02:30 nitrogen6x user.err kernel: tsc2004_prepare_for_reading: write_cmd -5
May 26 06:02:30 nitrogen6x user.warn kernel: tsc2004: probe of 2-0048 failed with error -5
May 26 06:02:30 nitrogen6x user.info kernel: check_alarm_past: alarm in the past
May 26 06:02:30 nitrogen6x user.info kernel: snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
May 26 06:02:30 nitrogen6x user.info kernel: i2c /dev entries driver
May 26 06:02:30 nitrogen6x user.info kernel: mxc_v4l2_output v4l2_out.37: V4L2 device registered as video16
May 26 06:02:30 nitrogen6x user.info kernel: mxc_v4l2_output v4l2_out.37: V4L2 device registered as video17
May 26 06:02:30 nitrogen6x user.warn kernel: i2c-core: driver [mag3110] using legacy suspend method
May 26 06:02:30 nitrogen6x user.warn kernel: i2c-core: driver [mag3110] using legacy resume method
May 26 06:02:30 nitrogen6x user.err kernel: imx_thermal tempmon.11: invalid sensor calibration data
May 26 06:02:30 nitrogen6x user.err kernel: imx_thermal tempmon.11: failed to get sensor data
May 26 06:02:30 nitrogen6x user.warn kernel: imx_thermal: probe of tempmon.11 failed with error -22
May 26 06:02:30 nitrogen6x user.info kernel: imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
May 26 06:02:30 nitrogen6x user.info kernel: cpuidle: using governor ladder
May 26 06:02:30 nitrogen6x user.info kernel: cpuidle: using governor menu
May 26 06:02:30 nitrogen6x user.info kernel: sdhci: Secure Digital Host Controller Interface driver
May 26 06:02:30 nitrogen6x user.info kernel: sdhci: Copyright(c) Pierre Ossman
May 26 06:02:30 nitrogen6x user.info kernel: sdhci-pltfm: SDHCI platform and OF driver helper
May 26 06:02:30 nitrogen6x user.warn kernel: sdhci-esdhc-imx 2194000.usdhc: could not get ultra high speed state, work on normal mode
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_dp_dc_disable: imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_suspend: imx-ipuv3 2400000.ipu: ipu busfreq high release.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:30 nitrogen6x user.warn kernel: imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 640x480 h_sync,r,l: 96,16,48 v_sync,l,u: 2,10,33 pixclock=25175000 Hz
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 640 x 480
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 25175000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:25142857
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:25142857
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:168, final_rate:4224000000, prate:264000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:10
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 00077C4F
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 08020000 01004000 00E7C000 F2C13FC0 00082CA0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 639,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 479,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 1279
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_enable_overflow_interrupts: hdmi_enable_overflow_interrupts
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.warn kernel: mmc0: Switching to 3.3V signalling voltage failed
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup - video mode changed
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_disable_overflow_interrupts: hdmi_disable_overflow_interrupts
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode used vic=0
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode vic=0 work in DVI
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: final pixclk = 24780000
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer exit
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.info kernel: mmc0: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
May 26 06:02:30 nitrogen6x user.warn kernel: sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
May 26 06:02:30 nitrogen6x user.info kernel: mmc1: no vqmmc regulator found
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.warn kernel: mmc0: Switching to 3.3V signalling voltage failed
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_enable_video_path: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_enable_video_path
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup exit
May 26 06:02:30 nitrogen6x user.warn kernel: mmc0: Switching to 3.3V signalling voltage failed
May 26 06:02:30 nitrogen6x user.info kernel: mmc1: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
May 26 06:02:30 nitrogen6x user.warn kernel: sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
May 26 06:02:30 nitrogen6x user.info kernel: mmc2: no vqmmc regulator found
May 26 06:02:30 nitrogen6x user.info kernel: mmc2: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
May 26 06:02:30 nitrogen6x user.warn kernel: mmc0: Switching to 3.3V signalling voltage failed
May 26 06:02:30 nitrogen6x user.warn kernel: mmc0: Switching to 3.3V signalling voltage failed
May 26 06:02:30 nitrogen6x user.info kernel: ata1: SATA link down (SStatus 0 SControl 300)
May 26 06:02:30 nitrogen6x user.info kernel: usb 1-1: new high-speed USB device number 2 using ci_hdrc
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_notify_fb: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb exit
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_notify_fb: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_disable: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_disable_overflow_interrupts: hdmi_disable_overflow_interrupts
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_disable: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable - exit
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_dp_dc_disable: imx-ipuv3 2400000.ipu: DC stop timeout - 1 * 10ms
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_suspend: imx-ipuv3 2400000.ipu: ipu busfreq high release.
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:30 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300000.
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:168, final_rate:2376000000, prate:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_dmfc_init: imx-ipuv3 2400000.ipu: DMFC high resolution has set, will not change
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 0010DCEF
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 08020000 01004000 00E7C000 F2C3BFC0 00082CA0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 1919,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 1079,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x40100000
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 3839
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:30 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.warn kernel: mmc2: host does not support reading read-only switch. assuming write-enable.
May 26 06:02:30 nitrogen6x user.info kernel: mmc2: new high speed SDHC card at address b368
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:30 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:30 nitrogen6x user.info kernel: mmcblk0: mmc2:b368 3.73 GiB
May 26 06:02:30 nitrogen6x user.info kernel: mmcblk0: p1 p2
May 26 06:02:30 nitrogen6x user.info kernel: hub 1-1:1.0: USB hub found
May 26 06:02:30 nitrogen6x user.info kernel: hub 1-1:1.0: 3 ports detected
May 26 06:02:30 nitrogen6x user.info kernel: Galcore version 4.6.9.9754
May 26 06:02:30 nitrogen6x user.debug kernel: vdoa_probe: mxc_vdoa 21e4000.vdoa: iram_base:0xc0880000,iram_paddr:0x904000,size:0x12000
May 26 06:02:30 nitrogen6x user.info kernel: mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
May 26 06:02:30 nitrogen6x user.info kernel: mxc_asrc 2034000.asrc: mxc_asrc registered
May 26 06:02:30 nitrogen6x user.info kernel: mxc_vpu 2040000.vpu: VPU initialized
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524)
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: job rings = 2, qi = 0
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-md5-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-md5-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-des3_ede-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-md5-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: ecb-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: ecb-arc4-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: ecb-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: ctr-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: cbc-aes-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: ecb-des3-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: cbc-3des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: cbc-des-caam
May 26 06:02:30 nitrogen6x user.info kernel: caam 2100000.caam: fsl,sec-v4.0 algorithms registered in /proc/crypto
May 26 06:02:30 nitrogen6x user.info kernel: platform 2101000.jr0: registering rng-caam
May 26 06:02:30 nitrogen6x user.info kernel: platform caam_sm: caam_sm_test: 8-byte key test match OK
May 26 06:02:30 nitrogen6x user.info kernel: platform caam_sm: caam_sm_test: 16-byte key test match OK
May 26 06:02:30 nitrogen6x user.info kernel: platform caam_sm: caam_sm_test: 32-byte key test match OK
May 26 06:02:30 nitrogen6x user.info kernel: platform caam_secvio.40: security violation service handlers armed
May 26 06:02:30 nitrogen6x user.info kernel: usbcore: registered new interface driver usbhid
May 26 06:02:30 nitrogen6x user.info kernel: usbhid: USB HID core driver
May 26 06:02:30 nitrogen6x user.err kernel: sgtl5000 0-000a: Failed to get supply 'VDDD': -19
May 26 06:02:30 nitrogen6x user.info kernel: 0-000a: 1200 mV normal
May 26 06:02:30 nitrogen6x user.info kernel: sgtl5000 0-000a: Using internal LDO instead of VDDD
May 26 06:02:30 nitrogen6x user.info kernel: sgtl5000 0-000a: sgtl5000 revision 0x11
May 26 06:02:30 nitrogen6x user.info kernel: imx-sgtl5000 sound.25: sgtl5000 <-> 2028000.ssi mapping ok
May 26 06:02:30 nitrogen6x user.info kernel: imx-audio-hdmi sound-hdmi.26: hdmi-hifi <-> hdmi_audio.16 mapping ok
May 26 06:02:30 nitrogen6x user.info kernel: TCP: cubic registered
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 10
May 26 06:02:30 nitrogen6x user.info kernel: sit: IPv6 over IPv4 tunneling driver
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 17
May 26 06:02:30 nitrogen6x user.info kernel: rfkill_gpio wlan_bt_rfkill.39: wlan_bt_rfkill device registered.
May 26 06:02:30 nitrogen6x user.notice kernel: Key type dns_resolver registered
May 26 06:02:30 nitrogen6x user.info kernel: VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
May 26 06:02:30 nitrogen6x user.notice kernel: Registering SWP/SWPB emulation handler
May 26 06:02:30 nitrogen6x user.info kernel: input: gpio-keys.24 as /devices/soc0/gpio-keys.24/input/input0
May 26 06:02:30 nitrogen6x user.info kernel: snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 2014-05-26 06:02:20 UTC (1401084140)
May 26 06:02:30 nitrogen6x user.info kernel: ALSA device list:
May 26 06:02:30 nitrogen6x user.info kernel: #0: imx6q-nitrogen6x-sgtl5000
May 26 06:02:30 nitrogen6x user.info kernel: #1: imx-hdmi-soc
May 26 06:02:30 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:30 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:30 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup - video mode changed
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: edid mode
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_disable_overflow_interrupts: hdmi_disable_overflow_interrupts
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode used vic=16
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode vic=16 work in DVI
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: final pixclk = 148500000
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer exit
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_enable_video_path: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_enable_video_path
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup exit
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_notify_fb: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb exit
May 26 06:02:30 nitrogen6x user.debug kernel: mxc_hdmi_cable_connected: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_cable_connected exit
May 26 06:02:30 nitrogen6x user.info kernel: kjournald starting. Commit interval 5 seconds
May 26 06:02:30 nitrogen6x user.info kernel: EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
May 26 06:02:30 nitrogen6x user.info kernel: VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
May 26 06:02:30 nitrogen6x user.info kernel: devtmpfs: mounted
May 26 06:02:30 nitrogen6x user.info kernel: Freeing unused kernel memory: 280K (807cd000 - 80813000)
May 26 06:02:30 nitrogen6x daemon.info kernel: udevd[161]: starting version 182
May 26 06:02:30 nitrogen6x user.debug kernel: evbug: Connected device: input0 (gpio-keys.24 at gpio-keys/input0)
May 26 06:02:30 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:30 nitrogen6x user.err kernel: update_device_addr: ov5642 ret=-5
May 26 06:02:30 nitrogen6x user.err kernel: ov5642_read_reg:write reg error:reg=300a
May 26 06:02:30 nitrogen6x user.warn kernel: camera ov5642 is not found
May 26 06:02:30 nitrogen6x user.info kernel: ov5640_mipi 1-003e: found pwm2, period=45
May 26 06:02:30 nitrogen6x user.err kernel: update_device_addr: ov5640_mipi ret=-5
May 26 06:02:30 nitrogen6x user.err kernel: ov5640_read_reg(mipi):reg=300a ret=-5
May 26 06:02:30 nitrogen6x user.warn kernel: camera ov5640_mipi is not found
May 26 06:02:30 nitrogen6x user.err kernel: mxc_v4l_open: Mxc Camera no sensor ipu0/csi1
May 26 06:02:30 nitrogen6x user.err kernel: mxc_v4l_open: Mxc Camera no sensor ipu1/csi1
May 26 06:02:30 nitrogen6x user.err kernel: mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
May 26 06:02:30 nitrogen6x user.warn kernel: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May 26 06:02:30 nitrogen6x user.info kernel: EXT3-fs (mmcblk0p2): using internal journal
May 26 06:02:30 nitrogen6x user.info kernel: fec 2188000.ethernet eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet:06, irq=188)
May 26 06:02:30 nitrogen6x user.info kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 06:02:30 nitrogen6x user.info kernel: libphy: 2188000.ethernet:06 - Link is Up - 100/Half
May 26 06:02:30 nitrogen6x user.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Found user 'avahi' (UID 998) and group 'avahi' (GID 998).
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Successfully dropped root privileges.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: avahi-daemon 0.6.31 starting up.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Successfully called chroot().
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Successfully dropped remaining capabilities.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Loading service file /services/sftp-ssh.service.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Loading service file /services/ssh.service.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.17.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: New relevant interface eth0.IPv4 for mDNS.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Network interface enumeration completed.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Registering new address record for fe80::219:b8ff:fe00:f2b2 on eth0.*.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Registering new address record for 192.168.2.17 on eth0.IPv4.
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
May 26 06:02:30 nitrogen6x daemon.info ofonod[687]: oFono version 1.14
May 26 06:02:30 nitrogen6x daemon.info neard[689]: NEAR daemon version 0.14
May 26 06:02:30 nitrogen6x user.info kernel: Bluetooth: Core ver 2.16
May 26 06:02:30 nitrogen6x user.info kernel: NET: Registered protocol family 31
May 26 06:02:30 nitrogen6x user.info kernel: Bluetooth: HCI device and connection manager initialized
May 26 06:02:30 nitrogen6x user.info kernel: Bluetooth: HCI socket layer initialized
May 26 06:02:30 nitrogen6x user.info kernel: Bluetooth: L2CAP socket layer initialized
May 26 06:02:30 nitrogen6x user.info kernel: Bluetooth: SCO socket layer initialized
May 26 06:02:30 nitrogen6x daemon.notice dbus[655]: [system] Activating service name='org.bluez' (using servicehelper)
May 26 06:02:30 nitrogen6x daemon.err neard[689]: Unable to find NFC netlink family
May 26 06:02:30 nitrogen6x daemon.err neard[689]: netlink init failed
May 26 06:02:30 nitrogen6x daemon.err neard[689]: *** NETLINK INITIALIZATION FAILED ***
May 26 06:02:30 nitrogen6x daemon.notice dbus[655]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1
May 26 06:02:30 nitrogen6x daemon.info avahi-daemon[683]: Server startup complete. Host name is nitrogen6x.local. Local service cookie is 3459518990.
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_dp_dc_disable: imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_runtime_suspend: imx-ipuv3 2400000.ipu: ipu busfreq high release.
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:31 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300006.
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_dmfc_init: imx-ipuv3 2400000.ipu: DMFC high resolution has set, will not change
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 0010DCEF
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 08020000 01004000 00E7C000 F2C3BFC0 00082CA0
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 1919,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 1079,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x40100000
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x40100000
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 3839
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:31 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:31 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:31 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:31 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:31 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:31 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:31 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:31 nitrogen6x daemon.info avahi-daemon[683]: Service "nitrogen6x" (/services/ssh.service) successfully established.
May 26 06:02:31 nitrogen6x daemon.info avahi-daemon[683]: Service "nitrogen6x" (/services/sftp-ssh.service) successfully established.
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_disable_channel: imx-ipuv3 2400000.ipu: ipu_disable_channel channel 157285631
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_dp_dc_disable: imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_uninit_channel: imx-ipuv3 2400000.ipu: ipu_uninit_channel
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_runtime_suspend: imx-ipuv3 2400000.ipu: ipu busfreq high release.
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_channel: imx-ipuv3 2400000.ipu: init channel = 9
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_runtime_resume: imx-ipuv3 2400000.ipu: ipu busfreq high requst.
May 26 06:02:33 nitrogen6x user.info kernel: mxc_sdc_fb fb.27: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300006.
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c09005c0
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_init: imx-ipuv3 2400000.ipu: initializing idma ch 23 @ c0901140 sub cpmem
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_dmfc_init: imx-ipuv3 2400000.ipu: DMFC high resolution has set, will not change
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 0 - 00000000 00000000 00000000 E0001800 0010DCEF
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: ch 23 word 1 - 09100000 01220000 00E7C000 F2C3BFC0 00082CA0
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: PFS 0x7,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: BPP 0x3,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: NPB 0x1f
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FW 1919,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: FH 1079,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA0 0x48800000
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: EBA1 0x48800000
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Stride 3839
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: scan_order 0
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: uv_stride 11424
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: u_offset 0x0
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: v_offset 0x0
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width0 4+1,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width1 5+1,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width2 4+1,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Width3 7+1,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset0 0,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset1 5,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset2 11,
May 26 06:02:33 nitrogen6x user.debug kernel: _ipu_ch_param_dump: imx-ipuv3 2400000.ipu: Offset3 16
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_enable_channel: imx-ipuv3 2400000.ipu: ipu_enable_channel channel 157285631
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_update_channel_offset: imx-ipuv3 2400000.ipu: ipu_update_channel_offset
May 26 06:02:33 nitrogen6x user.debug kernel: ipu_select_buffer: imx-ipuv3 2400000.ipu: ipu_select_buffer
May 26 06:02:33 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:33 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_fb_event: mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup - video mode changed
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: edid mode
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_disable_overflow_interrupts: hdmi_disable_overflow_interrupts
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode used vic=16
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: CEA mode vic=16 work in DVI
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: final pixclk = 148500000
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_av_composer: mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer exit
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_phy_init: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:33 nitrogen6x user.debug kernel: hdmi_phy_configure: mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_enable_video_path: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_enable_video_path
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
May 26 06:02:33 nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup exit
May 26 06:02:36 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:37 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
May 26 06:02:38 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: timeout when waiting for flip irq
May 26 06:02:39 nitrogen6x user.err kernel: mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0
May 26 06:02:52 nitrogen6x authpriv.notice login[714]: ROOT LOGIN on '/dev/ttymxc1'
May 26 06:04:09 nitrogen6x authpriv.info dropbear[734]: Child connection from 192.168.2.16:35366
May 26 06:04:09 nitrogen6x authpriv.notice dropbear[734]: Auth succeeded with blank password for 'root' from 192.168.2.16:35366
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-26 6:43 ` Peter Bergin
@ 2014-05-27 21:11 ` Eric Nelson
2014-05-28 6:51 ` Peter Bergin
0 siblings, 1 reply; 13+ messages in thread
From: Eric Nelson @ 2014-05-27 21:11 UTC (permalink / raw)
To: Peter Bergin, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
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.
I also notice in your output that you're running without the
"only_cea" flag, and you are getting a non-CEA mode:
mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
> I have also checked /sys/class/graphics/fb0 and made some tests.
>
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
> D:1920x1080p-60
This is really odd, because you're not seeing all of the
modes that are reported from U-Boot (e.g. 800x600@60):
> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
> D:720x480p-59
> D:720x576p-50
> D:1280x720p-50
> D:1280x720p-60
> D:1920x1080p-50
> V:640x480p-60
> D:1920x1080p-60
> V:640x480p-60
>
In your post on i.MX Community, you showed 15 "standard" timings:
https://community.freescale.com/thread/324175
Can you forward a hex-dump of your EDID settings from
U-Boot?
U-Boot > i2c dev 1
U-Boot > i2c md 50 0.1 200
0000: 00 ff ff ff ff ff ff 00 1e 6d fb 56 01 01 01 01 .........m.V....
0010: 03 13 01 03 80 33 1d 78 0a ae c5 a2 57 4a 9c 25 .....3.x....WJ.%
0020: 12 50 54 a7 6b 80 b3 00 81 8f 81 80 71 4f 01 01 .PT.k.......qO..
0030: 01 01 01 01 01 01 1a 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0
0040: 35 00 fe 22 11 00 00 1e 02 3a 80 18 71 38 2d 40 5..".....:..q8-@
0050: 53 2c 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 S,E..".........8
0060: 3d 1e 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc =.S... ....
0070: 00 57 32 33 36 31 0a 20 20 20 20 20 20 20 01 61 .W2361. .a
0080: 02 03 21 f1 4e 90 04 03 01 14 12 05 1f 10 13 00 ..!.N...........
0090: 00 00 00 23 09 07 07 83 01 00 00 65 03 0c 00 10 ...#.......e....
00a0: 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 fe 22 11 ..:..q8-@X,E..".
00b0: 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 fe .......q.. X,%..
00c0: 22 11 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 ".......rQ.. n(U
00d0: 00 fe 22 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 .."........ .-..
00e0: 3e 96 00 fe 22 11 00 00 18 00 00 00 00 00 00 00 >..."...........
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de ................
This might help narrow things down. We can fake the
EDID blob from there and see if we can reproduce
your symptoms.
> I have tried to set all of the above listed resolutions in modes. The
> only resolution that works is V:640x480p-60. With this resolution set I
> get signal on HDMI and the display shows my screen.
>
Also odd is that your 'mode' above shows 'D:1920x1080p-60'.
The 'D' stands for detailed, meaning that your EDID is
customizing the timings a bit from the standard.
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.10.17_1.0.0_ga/drivers/video/fbsysfs.c#L105
A couple of monitors here are showing "S"tandard timings:
root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
...
S:1920x1080p-60
Even though U-Boot shows "detailed" in the same manner as
your monitor:
U-Boot > i2c edid 50
EDID version: 1.3
Product ID code: 56fb
...
Estabilished timings:
...
Standard timings:
...
1920x1080 59 Hz (detailed)
1920x1080 60 Hz (detailed)
Monitor range limits, horizontal sync: 30-83 kHz, vertical
refresh: 56-61 Hz, max pixel clock: 150 MHz
Monitor name: W2361
Please advise,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-27 21:11 ` Eric Nelson
@ 2014-05-28 6:51 ` Peter Bergin
2014-05-28 14:02 ` Eric Nelson
0 siblings, 1 reply; 13+ messages in thread
From: Peter Bergin @ 2014-05-28 6:51 UTC (permalink / raw)
To: Eric Nelson, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
[-- Attachment #1: Type: text/plain, Size: 11494 bytes --]
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.
I have previously have the Nitrogen board running against this monitor and also other boards such as cgtqmx6. Your thought about silicon revision could be the case and the cause why we do not see the same behavior. Can someone at Freescale give us a hint if there are anything changed in this region that can cause this and if this is a valid guess?
If the "old revision" guess is a probable one we don't need to spend more time on this (from my point of view).
I also notice in your output that you're running without the
"only_cea" flag, and you are getting a non-CEA mode:
mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
I do running with only_cea flag. I think my kernel command line was cut in the log-file for some reason. My kernel command line looks like this:
root@nitrogen6x:~# cat /proc/cmdline
enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M dyndbg="module mxc_hdmi +pf;module mxc_hdmi_core +pf;module mxc_ipu +pf;module mxc_ipuv3_fb +pf" console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2 mxc_hdmi.only_cea=1
When looking in the driver code what the only_cea mode flag does is that it will only add CEA modes to the mode list. This is the cause why in the first case had 15 "standard" timings but in the second run after enabling the only_cea flag only have 8.
I have also checked /sys/class/graphics/fb0 and made some tests.
root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
D:1920x1080p-60
This is really odd, because you're not seeing all of the
modes that are reported from U-Boot (e.g. 800x600@60):
root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
D:720x480p-59
D:720x576p-50
D:1280x720p-50
D:1280x720p-60
D:1920x1080p-50
V:640x480p-60
D:1920x1080p-60
V:640x480p-60
In your post on i.MX Community, you showed 15 "standard" timings:
https://community.freescale.com/thread/324175
Can you forward a hex-dump of your EDID settings from
U-Boot?
U-Boot > i2c dev 1
U-Boot > i2c md 50 0.1 200
0000: 00 ff ff ff ff ff ff 00 1e 6d fb 56 01 01 01 01 .........m.V....
0010: 03 13 01 03 80 33 1d 78 0a ae c5 a2 57 4a 9c 25 .....3.x....WJ.%
0020: 12 50 54 a7 6b 80 b3 00 81 8f 81 80 71 4f 01 01 .PT.k.......qO..
0030: 01 01 01 01 01 01 1a 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0
0040: 35 00 fe 22 11 00 00 1e 02 3a 80 18 71 38 2d 40 5..".....:..q8-@
0050: 53 2c 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 S,E.."<mailto:.....:..q8-@0050:532c4500fe221100001e000000fd0038S,E..>.........8
0060: 3d 1e 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc =.S... ....
0070: 00 57 32 33 36 31 0a 20 20 20 20 20 20 20 01 61 .W2361. .a
0080: 02 03 21 f1 4e 90 04 03 01 14 12 05 1f 10 13 00 ..!.N...........
0090: 00 00 00 23 09 07 07 83 01 00 00 65 03 0c 00 10 ...#.......e....
00a0: 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 fe 22 11 ..:..q8-@X,E..".
00b0: 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 fe .......q.. X,%..
00c0: 22 11 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 ".......rQ.. n(U
00d0: 00 fe 22 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 .."........ .-..
00e0: 3e 96 00 fe 22 11 00 00 18 00 00 00 00 00 00 00 >..."...........
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de ................
This might help narrow things down. We can fake the
EDID blob from there and see if we can reproduce
your symptoms.
Here is a dump of EDID from my monitor. It is a Samsung SyncMaster B2440.
U-Boot > i2c dev 1
Setting bus to 1
U-Boot > i2c md 50 0.1 200
0000: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
0010: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
0020: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
0030: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
0040: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
0050: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
0060: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
0070: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
0080: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
0090: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
00a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
00b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%<mailto:U@.%>!....... @
00c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
00d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
0100: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
0110: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
0120: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
0130: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
0140: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
0150: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
0160: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
0170: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
0180: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
0190: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
01a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
01b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%<mailto:U@.%>!....... @
01c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
01d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
U-Boot >
I have tried to set all of the above listed resolutions in modes. The
only resolution that works is V:640x480p-60. With this resolution set I
get signal on HDMI and the display shows my screen.
One further observation I have done is regarding the clock source in the IPU. When running the working 640x480 resolution the IPU clock is internal but when running other non-working resolution the clock source is external (PLL5 ?). Could this be something that cause my problem?
640x480:
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 640 x 480
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 25200000
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 10:37:13 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 10:37:13 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:25142857
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:25142857
May 26 10:37:13 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:168, final_rate:4224000000, prate:264000000
May 26 10:37:13 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:10
1920x1080:
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: panel size = 1920 x 1080
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: pixel clk = 148500000
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu internal clk
May 26 10:23:06 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x1, di_gen reg:0x200006.
May 26 10:23:06 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:4224000000, prate:264000000
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: rounded pix clk:176000000
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: try ipu ext di clk
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: di clk:148500000
May 26 10:23:06 nitrogen6x user.debug kernel: _ipu_pixel_clk_set_parent: ipu_pixel_clk: di_clk_ext:0x0, di_gen reg:0x300006.
May 26 10:23:06 nitrogen6x user.debug kernel: _ipu_pixel_clk_div_recalc_rate: ipu_di0 read BS_CLKGEN0 div:16, final_rate:2376000000, prate:148500000
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: round pixel clk:148500000
May 26 10:23:06 nitrogen6x user.debug kernel: ipu_init_sync_panel: imx-ipuv3 2400000.ipu: div:1
Also odd is that your 'mode' above shows 'D:1920x1080p-60'.
The 'D' stands for detailed, meaning that your EDID is
customizing the timings a bit from the standard.
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.10.17_1.0.0_ga/drivers/video/fbsysfs.c#L105
A couple of monitors here are showing "S"tandard timings:
root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
...
S:1920x1080p-60
Even though U-Boot shows "detailed" in the same manner as
your monitor:
U-Boot > i2c edid 50
EDID version: 1.3
Product ID code: 56fb
...
Estabilished timings:
...
Standard timings:
...
1920x1080 59 Hz (detailed)
1920x1080 60 Hz (detailed)
Monitor range limits, horizontal sync: 30-83 kHz, vertical
refresh: 56-61 Hz, max pixel clock: 150 MHz
Monitor name: W2361
Please advise,
Eric
Thanks,
/Peter
[-- Attachment #2: Type: text/html, Size: 14614 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
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
0 siblings, 2 replies; 13+ messages in thread
From: Eric Nelson @ 2014-05-28 14:02 UTC (permalink / raw)
To: Peter Bergin, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
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.
>
> I have previously have the Nitrogen board running against this monitor
> and also other boards such as cgtqmx6. Your thought about silicon
> revision could be the case and the cause why we do not see the same
> behavior. Can someone at Freescale give us a hint if there are anything
> changed in this region that can cause this and if this is a valid guess?
>
> If the "old revision" guess is a probable one we don't need to spend
> more time on this (from my point of view).
>
I'd certainly like to know, since we have lots of other customers with
TO.1.0 silicon.
With this information and your EDID blob, I should be able to reproduce
things, and I'm sure I have an older board around somewhere.
>> I also notice in your output that you're running without the
>> "only_cea" flag, and you are getting a non-CEA mode:
>>
>> mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
>>
> I do running with only_cea flag. I think my kernel command line was cut
> in the log-file for some reason. My kernel command line looks like this:
>
> root@nitrogen6x:~# cat /proc/cmdline
> enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
> video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
> dyndbg="module mxc_hdmi +pf;module mxc_hdmi_core +pf;module mxc_ipu
> +pf;module mxc_ipuv3_fb +pf" console=ttymxc1,115200 vmalloc=400M
> consoleblank=0 rootwait root=/dev/mmcblk0p2 mxc_hdmi.only_cea=1
>
> When looking in the driver code what the only_cea mode flag does is that
> it will only add CEA modes to the mode list. This is the cause why in
> the first case had 15 "standard" timings but in the second run after
> enabling the only_cea flag only have 8.
>
Okay. I'm still confused about why the kernel decided to use
"DVI" mode.
Because of this, the kernel didn't configure an audio channel
as shown in my equivalent output:
nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi
20e0000.hdmi_video: mxc_hdmi_setup CEA mode
nitrogen6x user.debug kernel: hdmi_set_clk_regenerator:
hdmi_set_clk_regenerator: samplerate=48000 ratio=100
pixelclk=148500000 N=6144 cts=148500
nitrogen6x user.debug kernel: hdmi_enable_audio_clk: mxc_hdmi
20e0000.hdmi_video: hdmi_enable_audio_clk
nitrogen6x user.debug kernel: hdmi_config_AVI: mxc_hdmi
20e0000.hdmi_video: set up AVI frame
nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi
20e0000.hdmi_video: mxc_hdmi_setup exit
>>> I have also checked /sys/class/graphics/fb0 and made some tests.
>>>
>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>>> D:1920x1080p-60
>> This is really odd, because you're not seeing all of the
>> modes that are reported from U-Boot (e.g. 800x600@60):
>>
>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>>> D:720x480p-59
>>> D:720x576p-50
>>> D:1280x720p-50
>>> D:1280x720p-60
>>> D:1920x1080p-50
>>> V:640x480p-60
>>> D:1920x1080p-60
>>> V:640x480p-60
>>>
>> In your post on i.MX Community, you showed 15 "standard" timings:
>>
>> https://community.freescale.com/thread/324175
>>
>> Can you forward a hex-dump of your EDID settings from
>> U-Boot?
>>
>> U-Boot > i2c dev 1
>> U-Boot > i2c md 50 0.1 200
>> 0000: 00 ff ff ff ff ff ff 00 1e 6d fb 56 01 01 01 01 .........m.V....
>> 0010: 03 13 01 03 80 33 1d 78 0a ae c5 a2 57 4a 9c 25 .....3.x....WJ.%
>> 0020: 12 50 54 a7 6b 80 b3 00 81 8f 81 80 71 4f 01 01 .PT.k.......qO..
>> 0030: 01 01 01 01 01 01 1a 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0
>> 0040: 35 00 fe 22 11 00 00 1e 02 3a 80 18 71 38 2d 40 5..".....:..q8-@
>> 0050: 53 2c 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 S,E..".........8
>> 0060: 3d 1e 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc =.S... ....
>> 0070: 00 57 32 33 36 31 0a 20 20 20 20 20 20 20 01 61 .W2361. .a
>> 0080: 02 03 21 f1 4e 90 04 03 01 14 12 05 1f 10 13 00 ..!.N...........
>> 0090: 00 00 00 23 09 07 07 83 01 00 00 65 03 0c 00 10 ...#.......e....
>> 00a0: 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 fe 22 11 ..:..q8-@X,E..".
>> 00b0: 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 fe .......q.. X,%..
>> 00c0: 22 11 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 ".......rQ.. n(U
>> 00d0: 00 fe 22 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 .."........ .-..
>> 00e0: 3e 96 00 fe 22 11 00 00 18 00 00 00 00 00 00 00 >..."...........
>> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de ................
>>
>>
>> This might help narrow things down. We can fake the
>> EDID blob from there and see if we can reproduce
>> your symptoms.
> Here is a dump of EDID from my monitor. It is a Samsung SyncMaster B2440.
>
Thanks. This is helpful.
> U-Boot > i2c dev 1
> Setting bus to 1
> U-Boot > i2c md 50 0.1 200
> 0000: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
> 0010: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
> 0020: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
> 0030: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
> 0040: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
> 0050: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
> 0060: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
> 0070: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
> 0080: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
> 0090: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
> 00a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
> 00b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
> 00c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
> 00d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
> 00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
> 0100: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
> 0110: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
> 0120: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
> 0130: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
> 0140: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
> 0150: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
> 0160: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
> 0170: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
> 0180: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
> 0190: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
> 01a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
> 01b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
> 01c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
> 01d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
> 01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
> U-Boot >
>
>
>>> I have tried to set all of the above listed resolutions in modes. The
>>> only resolution that works is V:640x480p-60. With this resolution set I
>>> get signal on HDMI and the display shows my screen.
>>>
>
> One further observation I have done is regarding the clock source in the
> IPU. When running the working 640x480 resolution the IPU clock is
> internal but when running other non-working resolution the clock source
> is external (PLL5 ?). Could this be something that cause my problem?
>
Perhaps, but the clock divisors appeared to be the same as what
I saw in a working unit.
Regards,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-28 14:02 ` Eric Nelson
@ 2014-05-28 15:45 ` Haakon Stende
2014-05-28 16:09 ` Peter Bergin
1 sibling, 0 replies; 13+ messages in thread
From: Haakon Stende @ 2014-05-28 15:45 UTC (permalink / raw)
To: Eric Nelson
Cc: meta-freescale@yoctoproject.org, Peter Bergin, Otavio Salvador,
Troy
[-- Attachment #1: Type: text/plain, Size: 10277 bytes --]
I have a gk802 with cpu rev 1.0 and I also got some edid problems with the
new kernel that works ok on 3.0.35_4.1.0
The edid table is on 00's and then of course no sound on hdmi.
mxc_hdmi 20e0000.hdmi_video: Read EDID again
mxc_hdmi 20e0000.hdmi_video: No modes read from edid
mxc_hdmi 20e0000.hdmi_video: create default modelist
hste
2014-05-28 16:02 GMT+02:00 Eric Nelson <eric.nelson@boundarydevices.com>:
> 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.
>>>
>>
>> I have previously have the Nitrogen board running against this monitor
>> and also other boards such as cgtqmx6. Your thought about silicon
>> revision could be the case and the cause why we do not see the same
>> behavior. Can someone at Freescale give us a hint if there are anything
>> changed in this region that can cause this and if this is a valid guess?
>>
>> If the "old revision" guess is a probable one we don't need to spend
>> more time on this (from my point of view).
>>
>>
> I'd certainly like to know, since we have lots of other customers with
> TO.1.0 silicon.
>
> With this information and your EDID blob, I should be able to reproduce
> things, and I'm sure I have an older board around somewhere.
>
>
> I also notice in your output that you're running without the
>>> "only_cea" flag, and you are getting a non-CEA mode:
>>>
>>> mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI
>>> mode
>>>
>>> I do running with only_cea flag. I think my kernel command line was cut
>> in the log-file for some reason. My kernel command line looks like this:
>>
>> root@nitrogen6x:~# cat /proc/cmdline
>> enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
>> video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
>> dyndbg="module mxc_hdmi +pf;module mxc_hdmi_core +pf;module mxc_ipu
>> +pf;module mxc_ipuv3_fb +pf" console=ttymxc1,115200 vmalloc=400M
>> consoleblank=0 rootwait root=/dev/mmcblk0p2 mxc_hdmi.only_cea=1
>>
>> When looking in the driver code what the only_cea mode flag does is that
>> it will only add CEA modes to the mode list. This is the cause why in
>> the first case had 15 "standard" timings but in the second run after
>> enabling the only_cea flag only have 8.
>>
>>
> Okay. I'm still confused about why the kernel decided to use
> "DVI" mode.
>
> Because of this, the kernel didn't configure an audio channel
> as shown in my equivalent output:
>
> nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video:
> mxc_hdmi_setup CEA mode
> nitrogen6x user.debug kernel: hdmi_set_clk_regenerator:
> hdmi_set_clk_regenerator: samplerate=48000 ratio=100 pixelclk=148500000
> N=6144 cts=148500
> nitrogen6x user.debug kernel: hdmi_enable_audio_clk: mxc_hdmi
> 20e0000.hdmi_video: hdmi_enable_audio_clk
> nitrogen6x user.debug kernel: hdmi_config_AVI: mxc_hdmi
> 20e0000.hdmi_video: set up AVI frame
> nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video:
> mxc_hdmi_setup exit
>
>
> I have also checked /sys/class/graphics/fb0 and made some tests.
>>>>
>>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>>>> D:1920x1080p-60
>>>>
>>> This is really odd, because you're not seeing all of the
>>> modes that are reported from U-Boot (e.g. 800x600@60):
>>>
>>>
>>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>>>> D:720x480p-59
>>>> D:720x576p-50
>>>> D:1280x720p-50
>>>> D:1280x720p-60
>>>> D:1920x1080p-50
>>>> V:640x480p-60
>>>> D:1920x1080p-60
>>>> V:640x480p-60
>>>>
>>>> In your post on i.MX Community, you showed 15 "standard" timings:
>>>
>>> https://community.freescale.com/thread/324175
>>>
>>> Can you forward a hex-dump of your EDID settings from
>>> U-Boot?
>>>
>>> U-Boot > i2c dev 1
>>> U-Boot > i2c md 50 0.1 200
>>> 0000: 00 ff ff ff ff ff ff 00 1e 6d fb 56 01 01 01 01 .........m.V....
>>> 0010: 03 13 01 03 80 33 1d 78 0a ae c5 a2 57 4a 9c 25 .....3.x....WJ.%
>>> 0020: 12 50 54 a7 6b 80 b3 00 81 8f 81 80 71 4f 01 01 .PT.k.......qO..
>>> 0030: 01 01 01 01 01 01 1a 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0
>>> 0040: 35 00 fe 22 11 00 00 1e 02 3a 80 18 71 38 2d 40 5..".....:..q8-@
>>> 0050: 53 2c 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 S,E..".........8
>>> 0060: 3d 1e 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc =.S... ....
>>> 0070: 00 57 32 33 36 31 0a 20 20 20 20 20 20 20 01 61 .W2361. .a
>>> 0080: 02 03 21 f1 4e 90 04 03 01 14 12 05 1f 10 13 00 ..!.N...........
>>> 0090: 00 00 00 23 09 07 07 83 01 00 00 65 03 0c 00 10 ...#.......e....
>>> 00a0: 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 fe 22 11 ..:..q8-@X
>>> ,E..".
>>> 00b0: 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 fe .......q.. X,%..
>>> 00c0: 22 11 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 ".......rQ.. n(U
>>> 00d0: 00 fe 22 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 .."........ .-..
>>> 00e0: 3e 96 00 fe 22 11 00 00 18 00 00 00 00 00 00 00 >..."...........
>>> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de ................
>>>
>>>
>>> This might help narrow things down. We can fake the
>>> EDID blob from there and see if we can reproduce
>>> your symptoms.
>>>
>> Here is a dump of EDID from my monitor. It is a Samsung SyncMaster B2440.
>>
>>
> Thanks. This is helpful.
>
>
> U-Boot > i2c dev 1
>> Setting bus to 1
>> U-Boot > i2c md 50 0.1 200
>> 0000: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
>> 0010: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
>> 0020: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
>> 0030: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
>> 0040: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
>> 0050: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
>> 0060: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
>> 0070: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
>> 0080: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
>> 0090: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
>> 00a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
>> 00b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
>> 00c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
>> 00d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
>> 00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
>> 0100: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
>> 0110: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
>> 0120: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
>> 0130: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
>> 0140: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
>> 0150: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
>> 0160: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
>> 0170: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
>> 0180: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
>> 0190: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
>> 01a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
>> 01b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
>> 01c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
>> 01d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
>> 01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
>> U-Boot >
>>
>>
>> I have tried to set all of the above listed resolutions in modes. The
>>>> only resolution that works is V:640x480p-60. With this resolution set I
>>>> get signal on HDMI and the display shows my screen.
>>>>
>>>>
>> One further observation I have done is regarding the clock source in the
>> IPU. When running the working 640x480 resolution the IPU clock is
>> internal but when running other non-working resolution the clock source
>> is external (PLL5 ?). Could this be something that cause my problem?
>>
>>
> Perhaps, but the clock divisors appeared to be the same as what
> I saw in a working unit.
>
> Regards,
>
>
>
> Eric
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
[-- Attachment #2: Type: text/html, Size: 13029 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
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
1 sibling, 1 reply; 13+ messages in thread
From: Peter Bergin @ 2014-05-28 16:09 UTC (permalink / raw)
To: Eric Nelson, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
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.
>> I have previously have the Nitrogen board running against this monitor
>> and also other boards such as cgtqmx6. Your thought about silicon
>> revision could be the case and the cause why we do not see the same
>> behavior. Can someone at Freescale give us a hint if there are anything
>> changed in this region that can cause this and if this is a valid guess?
>>
>> If the "old revision" guess is a probable one we don't need to spend
>> more time on this (from my point of view).
>>
> I'd certainly like to know, since we have lots of other customers with
> TO.1.0 silicon.
>
> With this information and your EDID blob, I should be able to reproduce
> things, and I'm sure I have an older board around somewhere.
>
>>> I also notice in your output that you're running without the
>>> "only_cea" flag, and you are getting a non-CEA mode:
>>>
>>> mxc_hdmi_setup: mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup DVI mode
>>>
>> I do running with only_cea flag. I think my kernel command line was cut
>> in the log-file for some reason. My kernel command line looks like this:
>>
>> root@nitrogen6x:~# cat /proc/cmdline
>> enable_wait_mode=off video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
>> video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
>> dyndbg="module mxc_hdmi +pf;module mxc_hdmi_core +pf;module mxc_ipu
>> +pf;module mxc_ipuv3_fb +pf" console=ttymxc1,115200 vmalloc=400M
>> consoleblank=0 rootwait root=/dev/mmcblk0p2 mxc_hdmi.only_cea=1
>>
>> When looking in the driver code what the only_cea mode flag does is that
>> it will only add CEA modes to the mode list. This is the cause why in
>> the first case had 15 "standard" timings but in the second run after
>> enabling the only_cea flag only have 8.
>>
> Okay. I'm still confused about why the kernel decided to use
> "DVI" mode.
>
> Because of this, the kernel didn't configure an audio channel
> as shown in my equivalent output:
>
> nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi
> 20e0000.hdmi_video: mxc_hdmi_setup CEA mode
> nitrogen6x user.debug kernel: hdmi_set_clk_regenerator:
> hdmi_set_clk_regenerator: samplerate=48000 ratio=100
> pixelclk=148500000 N=6144 cts=148500
> nitrogen6x user.debug kernel: hdmi_enable_audio_clk: mxc_hdmi
> 20e0000.hdmi_video: hdmi_enable_audio_clk
> nitrogen6x user.debug kernel: hdmi_config_AVI: mxc_hdmi
> 20e0000.hdmi_video: set up AVI frame
> nitrogen6x user.debug kernel: mxc_hdmi_setup: mxc_hdmi
> 20e0000.hdmi_video: mxc_hdmi_setup exit
The reason for DVI mode and no audio is that I am using a HDMI to DVI
cable to the monitor.
>>>> I have also checked /sys/class/graphics/fb0 and made some tests.
>>>>
>>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>>>> D:1920x1080p-60
>>> This is really odd, because you're not seeing all of the
>>> modes that are reported from U-Boot (e.g. 800x600@60):
>>>
>>>> root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>>>> D:720x480p-59
>>>> D:720x576p-50
>>>> D:1280x720p-50
>>>> D:1280x720p-60
>>>> D:1920x1080p-50
>>>> V:640x480p-60
>>>> D:1920x1080p-60
>>>> V:640x480p-60
>>>>
>>> In your post on i.MX Community, you showed 15 "standard" timings:
>>>
>>> https://community.freescale.com/thread/324175
>>>
>>> Can you forward a hex-dump of your EDID settings from
>>> U-Boot?
>>>
>>> U-Boot > i2c dev 1
>>> U-Boot > i2c md 50 0.1 200
>>> 0000: 00 ff ff ff ff ff ff 00 1e 6d fb 56 01 01 01 01 .........m.V....
>>> 0010: 03 13 01 03 80 33 1d 78 0a ae c5 a2 57 4a 9c 25 .....3.x....WJ.%
>>> 0020: 12 50 54 a7 6b 80 b3 00 81 8f 81 80 71 4f 01 01 .PT.k.......qO..
>>> 0030: 01 01 01 01 01 01 1a 36 80 a0 70 38 1f 40 30 20 .......6..p8.@0
>>> 0040: 35 00 fe 22 11 00 00 1e 02 3a 80 18 71 38 2d 40 5..".....:..q8-@
>>> 0050: 53 2c 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 S,E..".........8
>>> 0060: 3d 1e 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc =.S... ....
>>> 0070: 00 57 32 33 36 31 0a 20 20 20 20 20 20 20 01 61 .W2361. .a
>>> 0080: 02 03 21 f1 4e 90 04 03 01 14 12 05 1f 10 13 00 ..!.N...........
>>> 0090: 00 00 00 23 09 07 07 83 01 00 00 65 03 0c 00 10 ...#.......e....
>>> 00a0: 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 fe 22 11 ..:..q8-@X,E..".
>>> 00b0: 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 fe .......q.. X,%..
>>> 00c0: 22 11 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 ".......rQ.. n(U
>>> 00d0: 00 fe 22 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 .."........ .-..
>>> 00e0: 3e 96 00 fe 22 11 00 00 18 00 00 00 00 00 00 00 >..."...........
>>> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de ................
>>>
>>>
>>> This might help narrow things down. We can fake the
>>> EDID blob from there and see if we can reproduce
>>> your symptoms.
>> Here is a dump of EDID from my monitor. It is a Samsung SyncMaster B2440.
>>
> Thanks. This is helpful.
>
>> U-Boot > i2c dev 1
>> Setting bus to 1
>> U-Boot > i2c md 50 0.1 200
>> 0000: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
>> 0010: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
>> 0020: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
>> 0030: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
>> 0040: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
>> 0050: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
>> 0060: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
>> 0070: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
>> 0080: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
>> 0090: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
>> 00a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
>> 00b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
>> 00c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
>> 00d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
>> 00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
>> 0100: 00 ff ff ff ff ff ff 00 4c 2d 9f 06 34 32 42 43 ........L-..42BC
>> 0110: 2c 14 01 03 80 34 1d 78 2a ee d1 a5 55 48 9b 26 ,....4.x*...UH.&
>> 0120: 12 50 54 bf ef 80 81 00 81 40 81 80 95 00 a9 40 .PT......@.....@
>> 0130: b3 00 71 4f 95 0f 02 3a 80 18 71 38 2d 40 58 2c ..qO...:..q8-@X,
>> 0140: 45 00 09 25 21 00 00 1e 00 00 00 fd 00 38 4b 1e E..%!........8K.
>> 0150: 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Q... .....S
>> 0160: 4d 42 32 34 34 30 4c 0a 20 20 20 20 00 00 00 ff MB2440L. ....
>> 0170: 00 48 39 58 5a 42 30 30 34 37 35 0a 20 20 01 a1 .H9XZB00475. ..
>> 0180: 02 01 04 00 02 3a 80 d0 72 38 2d 40 10 2c 45 80 .....:..r8-@.,E.
>> 0190: 09 25 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 .%!......rQ.. n(
>> 01a0: 55 00 09 25 21 00 00 1e 01 1d 00 bc 52 d0 1e 20 U..%!.......R..
>> 01b0: b8 28 55 40 09 25 21 00 00 1e 8c 0a d0 90 20 40 .(U@.%!....... @
>> 01c0: 31 20 0c 40 55 00 09 25 21 00 00 18 8c 0a d0 8a 1 .@U..%!.......
>> 01d0: 20 e0 2d 10 10 3e 96 00 09 25 21 00 00 18 00 00 .-..>...%!.....
>> 01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e ...............^
>> U-Boot >
>>
>>
>>>> I have tried to set all of the above listed resolutions in modes. The
>>>> only resolution that works is V:640x480p-60. With this resolution set I
>>>> get signal on HDMI and the display shows my screen.
>>>>
>> One further observation I have done is regarding the clock source in the
>> IPU. When running the working 640x480 resolution the IPU clock is
>> internal but when running other non-working resolution the clock source
>> is external (PLL5 ?). Could this be something that cause my problem?
>>
> Perhaps, but the clock divisors appeared to be the same as what
> I saw in a working unit.
>
> Regards,
>
>
> Eric
>
Regards,
/Peter
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-28 16:09 ` Peter Bergin
@ 2014-05-31 1:54 ` Eric Nelson
2014-05-31 21:16 ` Eric Nelson
0 siblings, 1 reply; 13+ messages in thread
From: Eric Nelson @ 2014-05-31 1:54 UTC (permalink / raw)
To: Peter Bergin, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: No HDMI signal from Nitrogen6x board with daisy
2014-05-31 1:54 ` Eric Nelson
@ 2014-05-31 21:16 ` Eric Nelson
0 siblings, 0 replies; 13+ messages in thread
From: Eric Nelson @ 2014-05-31 21:16 UTC (permalink / raw)
To: Peter Bergin, Otavio Salvador; +Cc: meta-freescale@yoctoproject.org, Troy
Hi all,
On 05/30/2014 06:54 PM, Eric Nelson wrote:
> 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>
>>>>>>
>>>>>
>>>>> 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.
>
Can anyone confirm 1080P HDMI support on 3.10.17 or
3.10.31 on other boards with TO 1.0?
I know it's been a long time since they stopped shipping,
but there must be some SABRE SD's or other boards around
with older silicon.
Please advise,
Eric
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2014-05-31 21:16 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-05-31 21:16 ` Eric Nelson
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.