Testing latest mx3_camera.c
Hi Guennadi & lists,
Which patchset should one use today to have latest and most stable "mx3_camera" driver in 2.6.29?
Until now, I have been using mx3_camera (/soc_camera) to interface a custom 7.5MPix 12bpp camera on a PCM037 based system running linux 2.6.28-next plus your November 2009 soc_camera patchset. I have also added support for 16 bit data in IDMAC driver though I have tested just 12.
I currently use OSELAS i.MX31 BSP Release 10, that is 2.6.29 plus a patch stack prepared by Sascha Hauer / Pengutronix. On top of that I am applying the "v4l-20090408" series from http://gross-embedded.homelinux.org/~lyakh/v4l-20090408/, with little merging effort.
--
Agustin Ferrin Pozuelo
Embedded Systems Consultant
http://embedded.ferrin.org
Tel. +34 610502587
Quoted 9 lines · Agustin
Which patchset should one use today to have latest and most stable "
mx3_camera" driver in 2.6.29?Until now, I have been using
mx3_camera(/soc_camera) to interface a custom 7.5MPix 12bpp camera on a PCM037 based system running linux 2.6.28-next plus your November 2009soc_camerapatchset. I have also added support for 16 bit data in IDMAC driver though I have tested just 12.
Quoted 5 lines
I currently use OSELAS i.MX31 BSP Release 10, that is 2.6.29 plus a patch stack prepared by Sascha Hauer / Pengutronix. On top of that I am applying the "v4l-20090408" series from
http://gross-embedded.homelinux.org/~lyakh/v4l-20090408/, with little merging effort.
Please, use http://marc.info/?l=linux-arm-kernel&m=123866462620240&w=2
also notice, which patches it needs. As a basis you can take linux-next or a suitable branch from git://git.pengutronix.de/git/imx/linux-2.6.git
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Hi Guennadi,
Quoted 10 lines · --- Guennadi Liakhovetski
Quoted 4 lines · Agustin
Which patchset should one use today to have latest and most stable "
mx3_camera" driver in 2.6.29?[snip]
Please, use http://marc.info/?l=linux-arm-kernel&m=123866462620240&w=2
also notice, which patches it needs. As a basis you can take linux-next or a suitable branch fromgit://git.pengutronix.de/git/imx/linux-2.6.git
I managed to merge your patch stack of 20090415 on top of Sascha's stack for 2.6.29. I think that is just before the "v4l-subdev" work. Then I adapted my code to work pretty much as your mt9p031 driver.
Now I get a timeout when trying to capture a single image, with the same hardware configuration that is working fine with 2.6.28-next.
I can see my "Sixcam" camera dumping a few frames before the timeout.
I am not sure where to look for the problem, so here is a debug dump in case you can point me in the right direction...
root@SixCam:~ insmod sixcam.kosixcam_mod_init(): ok
Sixcam TRIGGER on Sixcam board: ATA_CS0~MCU3_26 sixcam_i2c_probe(): ok
camera 0-0: mx3_camera: Set SENS_CONF to f00, rate 19523897 sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0 sixcam_video_probe(): probed camera.
mx3-camera mx3-camera.0: soc_camera: Allocated video_device c6080a00 sixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
root@SixCam:~ capture --bpp 8 --size 1536x1024
mx3-camera.0: mx3_camera: requested bus width 8 bit: 0
mx3-camera.0: mx3_camera: requested bus width 15 bit: 0
mx3-camera.0: mx3_camera: requested bus width 10 bit: 0
camera 0-0: soc_camera: Found 0 supported formats.
mx3-camera.0: mx3_camera: requested bus width 8 bit: 0
mx3-camera.0: mx3_camera: Providing format Monochrome 8 bit in pass-through mode mx3-camera.0: mx3_camera: requested bus width 15 bit: 0
mx3-camera.0: mx3_camera: Providing format Monochrome 16 bit in pass-through mode mx3-camera.0: mx3_camera: requested bus width 10 bit: 0
mx3-camera.0: mx3_camera: Providing format Sixcam 10-bit in pass-through mode camera 0-0: mx3_camera: Set SENS_CONF to f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0: soc_camera: camera device opensixcam_set_fmt(): 640x480+0+0sixcam_try_fmt(): icd->width=640 icd->height=480 fmt.pix.width=1536 fmt.pix.height=1024.
--> fmt.pix.width=1536 fmt.pix.height=1024.
ipu-core: ipu_idmac: timeout = 0 * 10ms
ipu-core: ipu_idmac: init channel = 7
ipu-core: ipu_idmac: IDMAC_CONF 0x70, IC_CONF 0x0, IDMAC_CHA_EN 0x0, IDMAC_CHA_PRI 0x80, IDMAC_CHA_BUSY 0x0
ipu-core: ipu_idmac: BUF0_RDY 0x0, BUF1_RDY 0x0, CUR_BUF 0x0, DB_MODE 0x0, TASKS_STAT 0x3
dma dma0chan7: ipu_idmac: Found channel 0x7, irq 176sixcam_set_fmt(): 1536x1024+0+0
camera 0-0: soc_camera: set width: 1536 height: 1024
mx3-camera.0: mx3_camera: requested bus width 8 bit: 0
mx3-camera.0: mx3_camera: Flags cam: 0x2695 host: 0xf0fd common: 0x2095sixcam_set_bus_param(): 0x2095
mx3-camera.0: mx3_camera: Set SENS_CONF to 708VIDIOC_S_FMT: width 1536, heightcamera 0-0: soc_camera: soc_camera_reqbufs: 1
1024, pixelformat = 'GREY'
mx3-camera.0: videobuf_dma_contig: __videobuf_mmap_free
camera 0-0: soc_camera: mmap called, vma=0xc4f886e0
mx3-camera.0: videobuf_dma_contig: __videobuf_mmap_mapper
mx3-camera.0: videobuf_dma_contig: dma_alloc_coherent data is at addr c9000000 (size 1572864) mx3-camera.0: videobuf_dma_contig: mmap c4fafec0: q=c8b63004 40147000-402c7000 (180000) pgoff 00084000 buf 0 mx3-camera.0: videobuf_dma_contig: vm_open c4fafec0 [count=0,vma=40147000-402c7000]
camera 0-0: soc_camera: vma start=0x40147000, size=1572864, ret=0
mx3-camera.0: videobuf_dma_contig: __videobuf_iolock memory method MMAP
camera 0-0: soc_camera: soc_camera_streamonsixcam_start_capture(): trigger on!
ipu-core: ipu_idmac: write param mem - addr = 0x00010070, data = 0x00000000
ipu-core: ipu_idmac: write param mem - addr = 0x00010071, data = 0x00004000
ipu-core: ipu_idmac: write param mem - addr = 0x00010072, data = 0x00000000
ipu-core: ipu_idmac: write param mem - addr = 0x00010073, data = 0xFF5FF000
ipu-core: ipu_idmac: write param mem - addr = 0x00010074, data = 0x00000003
ipu-core: ipu_idmac: write param mem - addr = 0x00010078, data = 0x84000000
ipu-core: ipu_idmac: write param mem - addr = 0x00010079, data = 0x00000000
ipu-core: ipu_idmac: write param mem - addr = 0x0001007A, data = 0x3E0E2FFB
ipu-core: ipu_idmac: write param mem - addr = 0x0001007B, data = 0x00000002
ipu-core: ipu_idmac: write param mem - addr = 0x0001007C, data = 0x00000000
dma dma0chan7: ipu_idmac: Submitting sg c4e0772c
dma dma0chan7: ipu_idmac: Updated sg c4e0772c on channel 0x7 buffer 0
ipu-core: ipu_idmac: IDMAC_CONF 0x70, IC_CONF 0x0, IDMAC_CHA_EN 0x0, IDMAC_CHA_PRI 0x80, IDMAC_CHA_BUSY 0x0
ipu-core: ipu_idmac: BUF0_RDY 0x80, BUF1_RDY 0x0, CUR_BUF 0x0, DB_MODE 0x0, TASKS_STAT 0x3
ipu-core: ipu_idmac: IDMAC_CONF 0x70, IC_CONF 0x40000001, IDMAC_CHA_EN 0x80, IDMAC_CHA_PRI 0x80, IDMAC_CHA_BUSY 0x0
ipu-core: ipu_idmac: BUF0_RDY 0x80, BUF1_RDY 0x0, CUR_BUF 0x0, DB_MODE 0x0, TASKS_STAT 0x3 camera 0-0: mx3_camera: Submitted cookie 2 DMA 0x84000000
dma dma0chan7: ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7: ipu_idmac: IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0!
[ ten seconds pass, and a lot of frames come out of my camera ]
capture: Select timeout. Exiting...
mx3-camera.0: videobuf_dma_contig: vm_close c4fafec0 [count=1,vma=40147000-402c7000] mx3-camera.0: videobuf_dma_contig: munmap c4fafec0 q=c8b63004
camera 0-0: mx3_camera: Release active DMA 0x84000000 (state 3), queue not empty camera 0-0: mx3_camera: free_buffer (vb=0xc4e076c0) 0x40147000 1572864 mx3-camera.0: videobuf_dma_contig: buf[0] freeing c9000000
ipu-core: ipu_idmac: timeout = 0 * 10mssixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
camera 0-0: soc_camera: camera device close
Any clue?
BTW, this dump shows a few apparently unneeded calls to camera set_fmt() and get_bus_params().
Many thanks,
--Agustín.
--
Agustin Ferrin Pozuelo
Embedded Systems Consultant
http://embedded.ferrin.org
Tel. +34 610502587
Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Quoted 15 lines · Agustin
Hi Guennadi,
Quoted 10 lines · --- Guennadi Liakhovetski
Quoted 4 lines · Agustin
Which patchset should one use today to have latest and most stable "
mx3_camera" driver in 2.6.29?[snip]
Please, use http://marc.info/?l=linux-arm-kernel&m=123866462620240&w=2
also notice, which patches it needs. As a basis you can take linux-next or a suitable branch fromgit://git.pengutronix.de/git/imx/linux-2.6.git
Quoted 7 lines
I managed to merge your patch stack of 20090415 on top of Sascha's stack for 2.6.29. I think that is just before the "v4l-subdev" work. Then I adapted my code to work pretty much as your mt9p031 driver.
Now I get a timeout when trying to capture a single image, with the same hardware configuration that is working fine with 2.6.28-next.
I can see my "Sixcam" camera dumping a few frames before the timeout.
Have you applied this patch:
Author: Ming Lei <[email protected]> Date: Fri Mar 27 21:50:00 2009 +0800
driver core: fix driver_match_device
This patch fixes a bug introduced in commit
49b420a13ff95b449947181190b08367348e3e1b.
If a instance of bus_type doesn't have .match method, all .probe of drivers in the bus should be called, or else the .probe have not a chance to be called.
?
Thanks
Guennadi
Quoted 95 lines
I am not sure where to look for the problem, so here is a debug dump in case you can point me in the right direction...
root@SixCam:~ insmod sixcam.ko
sixcam_mod_init(): ok
Sixcam TRIGGER on Sixcam board: ATA_CS0~MCU3_26sixcam_i2c_probe(): ok
camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0sixcam_video_probe(): probed camera.
mx3-camera mx3-camera.0:soc_camera: Allocatedvideo_devicec6080a00sixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0root@SixCam:~ capture --bpp 8 --size 1536x1024
mx3-camera.0:mx3_camera: requested bus width 8 bit: 0
mx3-camera.0:mx3_camera: requested bus width 15 bit: 0
mx3-camera.0:mx3_camera: requested bus width 10 bit: 0
camera 0-0:soc_camera: Found 0 supported formats.
mx3-camera.0:mx3_camera: requested bus width 8 bit: 0
mx3-camera.0:mx3_camera: Providing format Monochrome 8 bit in pass-through mode mx3-camera.0:mx3_camera: requested bus width 15 bit: 0
mx3-camera.0:mx3_camera: Providing format Monochrome 16 bit in pass-through mode mx3-camera.0:mx3_camera: requested bus width 10 bit: 0
mx3-camera.0:mx3_camera: Providing format Sixcam 10-bit in pass-through mode camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0:soc_camera: camera device opensixcam_set_fmt(): 640x480+0+0sixcam_try_fmt(): icd->width=640 icd->height=480 fmt.pix.width=1536 fmt.pix.height=1024.--> fmt.pix.width=1536 fmt.pix.height=1024.ipu-core:
ipu_idmac: timeout = 0 * 10ms
ipu-core:ipu_idmac: init channel = 7
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0
ipu-core:ipu_idmac:BUF0_RDY0x0,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,TASKS_STAT0x3
dma dma0chan7:ipu_idmac: Found channel0x7, irq 176sixcam_set_fmt(): 1536x1024+0+0
camera 0-0:soc_camera: set width: 1536 height: 1024
mx3-camera.0:mx3_camera: requested bus width 8 bit: 0
mx3-camera.0:mx3_camera: Flags cam:0x2695host:0xf0fdcommon:0x2095sixcam_set_bus_param():0x2095
mx3-camera.0:mx3_camera: SetSENS_CONFto 708VIDIOC_S_FMT: width 1536, heightcamera 0-0:soc_camera:soc_camera_reqbufs: 1
1024, pixelformat = 'GREY'
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_free
camera 0-0:soc_camera: mmap called, vma=0xc4f886e0
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_mapper
mx3-camera.0:videobuf_dma_contig:dma_alloc_coherentdata is at addrc9000000(size 1572864) mx3-camera.0:videobuf_dma_contig: mmapc4fafec0: q=c8b63004 40147000-402c7000 (180000) pgoff 00084000 buf 0 mx3-camera.0:videobuf_dma_contig:vm_openc4fafec0[count=0,vma=40147000-402c7000]
camera 0-0:soc_camera: vma start=0x40147000, size=1572864, ret=0
mx3-camera.0:videobuf_dma_contig:__videobuf_iolockmemory method MMAP
camera 0-0:soc_camera:soc_camera_streamonsixcam_start_capture(): trigger on!
ipu-core:ipu_idmac: write param mem - addr =0x00010070, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010071, data =0x00004000
ipu-core:ipu_idmac: write param mem - addr =0x00010072, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010073, data =0xFF5FF000
ipu-core:ipu_idmac: write param mem - addr =0x00010074, data =0x00000003
ipu-core:ipu_idmac: write param mem - addr =0x00010078, data =0x84000000
ipu-core:ipu_idmac: write param mem - addr =0x00010079, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x0001007A, data =0x3E0E2FFB
ipu-core:ipu_idmac: write param mem - addr =0x0001007B, data =0x00000002
ipu-core:ipu_idmac: write param mem - addr =0x0001007C, data =0x00000000
dma dma0chan7:ipu_idmac: Submitting sgc4e0772c
dma dma0chan7:ipu_idmac: Updated sgc4e0772con channel0x7buffer 0
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0
ipu-core:ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,TASKS_STAT0x3
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x40000001,IDMAC_CHA_EN0x80,IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0
ipu-core:ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,TASKS_STAT0x3camera 0-0:mx3_camera: Submitted cookie 2 DMA0x84000000
dma dma0chan7:ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7:ipu_idmac: IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0![ ten seconds pass, and a lot of frames come out of my camera ]
capture: Select timeout. Exiting...
mx3-camera.0:videobuf_dma_contig:vm_closec4fafec0[count=1,vma=40147000-402c7000] mx3-camera.0:videobuf_dma_contig: munmapc4fafec0q=c8b63004
camera 0-0:mx3_camera: Release active DMA0x84000000(state 3), queue not empty camera 0-0:mx3_camera:free_buffer(vb=0xc4e076c0)0x401470001572864 mx3-camera.0:videobuf_dma_contig: buf[0] freeingc9000000
ipu-core:ipu_idmac: timeout = 0 * 10mssixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
camera 0-0:soc_camera: camera device closeAny clue?
BTW, this dump shows a few apparently unneeded calls to camera
set_fmt()andget_bus_params().
Quoted 9 lines
Many thanks,
--Agustín.--
Agustin Ferrin Pozuelo
Embedded Systems Consultant
http://embedded.ferrin.org
Tel. +34 610502587
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Quoted 43 lines · Guennadi Liakhovetski
Quoted 9 lines · Agustin
Hi Guennadi,
Quoted 5 lines · --- Guennadi Liakhovetski
Quoted 3 lines · Agustin
Which patchset should one use today to have latest and most stable "
mx3_camera" driver in 2.6.29?Quoted 7 lines
Quoted 5 lines
Quoted 1 line
[snip]
Please, use http://marc.info/?l=linux-arm-kernel&m=123866462620240&w=2
also notice, which patches it needs. As a basis you can take linux-next or a suitable branch fromgit://git.pengutronix.de/git/imx/linux-2.6.gitI managed to merge your patch stack of 20090415 on top of Sascha's stack for
2.6.29.
Quoted 1 line
I think that is just before the "v4l-subdev" work. Then I adapted my code to
work pretty
Quoted 3 lines
much as your mt9p031 driver.
Now I get a timeout when trying to capture a single image, with the same
hardware
Quoted 2 lines
configuration that is working fine with 2.6.28-next.
I can see my "Sixcam" camera dumping a few frames before the timeout.Have you applied this patch:
Author: Ming Lei Date: Fri Mar 27 21:50:00 2009 +0800driver core: fix
driver_match_deviceThis patch fixes a bug introduced in commit
49b420a13ff95b449947181190b08367348e3e1b.If a instance of
bus_typedoesn't have .match method, all .probe of drivers in the bus should be called, or else the .probe have not a chance to be called.
Quoted 5 lines
Signed-off-by Ming LeiReported-by Guennadi LiakhovetskiSigned-off-by Greg Kroah-Hartman?
No, as there is no driver_match_device() in 2.6.29 nor in my patched version. How important is that?
Meanwhile I noticed that IRQ 176 is being triggered, then discarded as "unhandled" by ipu_idmac, who gives the message "IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0!" below...
Quoted 126 lines
Quoted 2 lines
I am not sure where to look for the problem, so here is a debug dump in case
you can
Quoted 15 lines
point me in the right direction...
root@SixCam:~ insmod sixcam.ko
sixcam_mod_init(): ok
Sixcam TRIGGER on Sixcam board: ATA_CS0~MCU3_26sixcam_i2c_probe(): ok
camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0sixcam_video_probe(): probed camera.
mx3-camera mx3-camera.0:soc_camera: Allocatedvideo_devicec6080a00sixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0Quoted 7 lines
root@SixCam:~ capture --bpp 8 --size 1536x1024
mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: requested bus width 10 bit: 0
camera 0-0:soc_camera: Found 0 supported formats. mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 8 bit in pass-throughmode
Quoted 2 lines
mx3-camera.0:
mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 16 bit in pass-throughmode
Quoted 8 lines
mx3-camera.0:
mx3_camera: requested bus width 10 bit: 0 mx3-camera.0:mx3_camera: Providing format Sixcam 10-bit in pass-through mode camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0:soc_camera: camera device opensixcam_set_fmt(): 640x480+0+0sixcam_try_fmt(): icd->width=640 icd->height=480 fmt.pix.width=1536fmt.pix.height=1024.
Quoted 4 lines
--> fmt.pix.width=1536 fmt.pix.height=1024.ipu-core:
ipu_idmac: timeout = 0 * 10ms
ipu-core:ipu_idmac: init channel = 7
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x0,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 5 lines
dma dma0chan7:
ipu_idmac: Found channel0x7, irq 176sixcam_set_fmt(): 1536x1024+0+0
camera 0-0:soc_camera: set width: 1536 height: 1024 mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Flags cam:0x2695host:0xf0fdcommon:0x2095Quoted 8 lines
sixcam_set_bus_param():0x2095
mx3-camera.0:mx3_camera: SetSENS_CONFto 708VIDIOC_S_FMT: width 1536, heightcamera 0-0:soc_camera:soc_camera_reqbufs: 1
1024, pixelformat = 'GREY'
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_free
camera 0-0:soc_camera: mmap called, vma=0xc4f886e0
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_mappermx3-camera.0:videobuf_dma_contig:dma_alloc_coherentdata is at addrc9000000(size 1572864)
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig: mmapc4fafec0: q=c8b63004 40147000-402c7000(180000) pgoff 00084000 buf 0
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig:vm_openc4fafec0[count=0,vma=40147000-402c7000]
Quoted 9 lines
camera 0-0:
soc_camera: vma start=0x40147000, size=1572864, ret=0 mx3-camera.0:videobuf_dma_contig:__videobuf_iolockmemory method MMAP camera 0-0:soc_camera:soc_camera_streamonsixcam_start_capture(): trigger on!
ipu-core:ipu_idmac: write param mem - addr =0x00010070, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010071, data =0x00004000
ipu-core:ipu_idmac: write param mem - addr =0x00010072, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010073, data =0xFF5FF000
ipu-core:ipu_idmac: write param mem - addr =0x00010074, data =0x00000003Quoted 8 lines
ipu-core:
ipu_idmac: write param mem - addr =0x00010078, data =0x84000000
ipu-core:ipu_idmac: write param mem - addr =0x00010079, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x0001007A, data =0x3E0E2FFB
ipu-core:ipu_idmac: write param mem - addr =0x0001007B, data =0x00000002
ipu-core:ipu_idmac: write param mem - addr =0x0001007C, data =0x00000000dma dma0chan7:ipu_idmac: Submitting sgc4e0772c
dma dma0chan7:ipu_idmac: Updated sgc4e0772con channel0x7buffer 0
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 1 line
ipu-core:
ipu_idmac:IDMAC_CONF0x70,IC_CONF0x40000001,IDMAC_CHA_EN0x80,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 3 lines
camera 0-0:
mx3_camera: Submitted cookie 2 DMA0x84000000
dma dma0chan7:ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7:ipu_idmac: IRQ on active buffer on channel 7, active 0, ready0, 0, current 0!
Quoted 5 lines
[ ten seconds pass, and a lot of frames come out of my camera ]
capture: Select timeout. Exiting... mx3-camera.0:
videobuf_dma_contig:vm_closec4fafec0[count=1,vma=40147000-402c7000]
Quoted 2 lines
mx3-camera.0:
videobuf_dma_contig: munmapc4fafec0q=c8b63004 camera 0-0:mx3_camera: Release active DMA0x84000000(state 3), queue notempty
Quoted 10 lines
camera 0-0:
mx3_camera:free_buffer(vb=0xc4e076c0)0x401470001572864 mx3-camera.0:videobuf_dma_contig: buf[0] freeingc9000000
ipu-core:ipu_idmac: timeout = 0 * 10mssixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
camera 0-0:soc_camera: camera device closeAny clue?
BTW, this dump shows a few apparently unneeded calls to camera
set_fmt()and
get_bus_params().Quoted 10 lines
Many thanks,
--Agustín.--
Agustin Ferrin Pozuelo
Embedded Systems Consultant
http://embedded.ferrin.org
Tel. +34 610502587---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Quoted 2 lines · Agustin
No, as there is no
driver_match_device()in 2.6.29 nor in my patched version. How important is that?
No, sorry, forget it, that's not your problem.
Quoted 3 lines
Meanwhile I noticed that IRQ 176 is being triggered, then discarded as "unhandled" by
ipu_idmac, who gives the message "IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0!" below...
Yes, and this is not good. If you look in drivers/dma/ipu/ipu_idmac.c idmac_interrupt() you'll see, that this message is printed when IDMAC produces an interrupt for a DMA buffer, but at the same time it says, that the buffer, that should have completed is still in use... I've seen a few of such inconsistencies, and up to now always managed to get rid of them in one or another way. But that should not be related to the conversion. Maybe your formats on the sensor and on the SoC do not match, verify that.
Thanks
Guennadi
Quoted 106 lines
Quoted 106 lines
Quoted 1 line
I am not sure where to look for the problem, so here is a debug dump in case
you can
Quoted 15 lines
point me in the right direction...
root@SixCam:~ insmod sixcam.ko
sixcam_mod_init(): ok
Sixcam TRIGGER on Sixcam board: ATA_CS0~MCU3_26sixcam_i2c_probe(): ok
camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0sixcam_video_probe(): probed camera.
mx3-camera mx3-camera.0:soc_camera: Allocatedvideo_devicec6080a00sixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0Quoted 7 lines
root@SixCam:~ capture --bpp 8 --size 1536x1024
mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: requested bus width 10 bit: 0
camera 0-0:soc_camera: Found 0 supported formats. mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 8 bit in pass-throughmode
Quoted 2 lines
mx3-camera.0:
mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 16 bit in pass-throughmode
Quoted 8 lines
mx3-camera.0:
mx3_camera: requested bus width 10 bit: 0 mx3-camera.0:mx3_camera: Providing format Sixcam 10-bit in pass-through mode camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0
camera 0-0:soc_camera: camera device opensixcam_set_fmt(): 640x480+0+0sixcam_try_fmt(): icd->width=640 icd->height=480 fmt.pix.width=1536fmt.pix.height=1024.
Quoted 4 lines
--> fmt.pix.width=1536 fmt.pix.height=1024.ipu-core:
ipu_idmac: timeout = 0 * 10ms
ipu-core:ipu_idmac: init channel = 7
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x0,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 5 lines
dma dma0chan7:
ipu_idmac: Found channel0x7, irq 176sixcam_set_fmt(): 1536x1024+0+0
camera 0-0:soc_camera: set width: 1536 height: 1024 mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Flags cam:0x2695host:0xf0fdcommon:0x2095Quoted 8 lines
sixcam_set_bus_param():0x2095
mx3-camera.0:mx3_camera: SetSENS_CONFto 708VIDIOC_S_FMT: width 1536, heightcamera 0-0:soc_camera:soc_camera_reqbufs: 1
1024, pixelformat = 'GREY'
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_free
camera 0-0:soc_camera: mmap called, vma=0xc4f886e0
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_mappermx3-camera.0:videobuf_dma_contig:dma_alloc_coherentdata is at addrc9000000(size 1572864)
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig: mmapc4fafec0: q=c8b63004 40147000-402c7000(180000) pgoff 00084000 buf 0
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig:vm_openc4fafec0[count=0,vma=40147000-402c7000]
Quoted 9 lines
camera 0-0:
soc_camera: vma start=0x40147000, size=1572864, ret=0 mx3-camera.0:videobuf_dma_contig:__videobuf_iolockmemory method MMAP camera 0-0:soc_camera:soc_camera_streamonsixcam_start_capture(): trigger on!
ipu-core:ipu_idmac: write param mem - addr =0x00010070, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010071, data =0x00004000
ipu-core:ipu_idmac: write param mem - addr =0x00010072, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x00010073, data =0xFF5FF000
ipu-core:ipu_idmac: write param mem - addr =0x00010074, data =0x00000003Quoted 8 lines
ipu-core:
ipu_idmac: write param mem - addr =0x00010078, data =0x84000000
ipu-core:ipu_idmac: write param mem - addr =0x00010079, data =0x00000000
ipu-core:ipu_idmac: write param mem - addr =0x0001007A, data =0x3E0E2FFB
ipu-core:ipu_idmac: write param mem - addr =0x0001007B, data =0x00000002
ipu-core:ipu_idmac: write param mem - addr =0x0001007C, data =0x00000000dma dma0chan7:ipu_idmac: Submitting sgc4e0772c
dma dma0chan7:ipu_idmac: Updated sgc4e0772con channel0x7buffer 0
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 1 line
ipu-core:
ipu_idmac:IDMAC_CONF0x70,IC_CONF0x40000001,IDMAC_CHA_EN0x80,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 3 lines
camera 0-0:
mx3_camera: Submitted cookie 2 DMA0x84000000
dma dma0chan7:ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7:ipu_idmac: IRQ on active buffer on channel 7, active 0, ready0, 0, current 0!
Quoted 5 lines
[ ten seconds pass, and a lot of frames come out of my camera ]
capture: Select timeout. Exiting... mx3-camera.0:
videobuf_dma_contig:vm_closec4fafec0[count=1,vma=40147000-402c7000]
Quoted 2 lines
mx3-camera.0:
videobuf_dma_contig: munmapc4fafec0q=c8b63004 camera 0-0:mx3_camera: Release active DMA0x84000000(state 3), queue notempty
Quoted 7 lines
camera 0-0:
mx3_camera:free_buffer(vb=0xc4e076c0)0x401470001572864 mx3-camera.0:videobuf_dma_contig: buf[0] freeingc9000000
ipu-core:ipu_idmac: timeout = 0 * 10mssixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
camera 0-0:soc_camera: camera device close
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Any clue?
BTW, this dump shows a few apparently unneeded calls to camera
set_fmt()and
get_bus_params().
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Quoted 12 lines · Guennadi Liakhovetski
Quoted 2 lines · Agustin
No, as there is no
driver_match_device()in 2.6.29 nor in my patched version. How important is that?No, sorry, forget it, that's not your problem.
Quoted 3 lines
Meanwhile I noticed that IRQ 176 is being triggered, then discarded as "unhandled" by
ipu_idmac, who gives the message "IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0!" below...
Quoted 7 lines
Yes, and this is not good. If you look in
drivers/dma/ipu/ipu_idmac.cidmac_interrupt()you'll see, that this message is printed when IDMAC produces an interrupt for a DMA buffer, but at the same time it says, that the buffer, that should have completed is still in use... I've seen a few of such inconsistencies, and up to now always managed to get rid of them in one or another way. But that should not be related to the conversion. Maybe your formats on the sensor and on the SoC do not match, verify that.
Thanks for the tip but I am still out of luck. I enabled DEBUG in ipu_idmac.c just to see that frame start and end are happening more or less when they should:
[...]
camera 0-0: mx3_camera: Submitted cookie 2 DMA 0x86400000
Got SOF IRQ 177 on Channel 7
Got EOF IRQ 178 on Channel 7
dma dma0chan7: ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7: ipu_idmac: IRQ on active buffer on channel 7, active 0, ready 0, 0, current 0! Select timeout.
[...]
I also configured everything to the simplest mode I can have: 8-bit bus, sample falling.
So I am now looking at IDMAC, trying to guess what could be wrong, but I feel quite lost at the moment. I am starting to fear that I introduced some subtle bug while merging your stack into Sascha's... Where can I check mx3_camera.c, ipu_idmac.c, soc_camera.c prior to the subdev changes? I would like them to check that my edited patches lead to the same sources as the originals.
Thanks & regards,
--Agustín.
Quoted 140 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
I am not sure where to look for the problem, so here is a debug dump in
case
Quoted 16 lines
Quoted 16 lines
you can
Quoted 15 lines
point me in the right direction...
root@SixCam:~ insmod sixcam.ko
sixcam_mod_init(): ok
Sixcam TRIGGER on Sixcam board: ATA_CS0~MCU3_26sixcam_i2c_probe(): ok
camera 0-0:mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0sixcam_video_probe(): probed camera.
mx3-camera mx3-camera.0:soc_camera: Allocatedvideo_devicec6080a00sixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
root@SixCam:~ capture --bpp 8 --size 1536x1024 mx3-camera.0:
mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: requested bus width 10 bit: 0 camera 0-0:soc_camera: Found 0 supported formats. mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 8 bit inpass-through
Quoted 3 lines
Quoted 3 lines
mode
Quoted 2 lines
mx3-camera.0:
mx3_camera: requested bus width 15 bit: 0 mx3-camera.0:mx3_camera: Providing format Monochrome 16 bit inpass-through
Quoted 3 lines
Quoted 3 lines
mode
Quoted 2 lines
mx3-camera.0:
mx3_camera: requested bus width 10 bit: 0 mx3-camera.0:mx3_camera: Providing format Sixcam 10-bit in pass-throughmode
Quoted 15 lines
Quoted 15 lines
Quoted 6 lines
camera 0-0:
mx3_camera: SetSENS_CONFto f00, rate 19523897sixcam_init(): initialized camera.
camera 0-0: MX3 Camera driver attached to camera 0 camera 0-0:soc_camera: camera device opensixcam_set_fmt(): 640x480+0+0sixcam_try_fmt(): icd->width=640 icd->height=480 fmt.pix.width=1536fmt.pix.height=1024.
Quoted 4 lines
--> fmt.pix.width=1536 fmt.pix.height=1024.ipu-core:
ipu_idmac: timeout = 0 * 10ms
ipu-core:ipu_idmac: init channel = 7
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x0,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE0x0,
TASKS_STAT0x3Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
dma dma0chan7:
ipu_idmac: Found channel0x7, irq 176sixcam_set_fmt(): 1536x1024+0+0
camera 0-0:soc_camera: set width: 1536 height: 1024 mx3-camera.0:mx3_camera: requested bus width 8 bit: 0 mx3-camera.0:mx3_camera: Flags cam:0x2695host:0xf0fdcommon:0x2095sixcam_set_bus_param():0x2095
mx3-camera.0:mx3_camera: SetSENS_CONFto 708VIDIOC_S_FMT: width 1536, heightcamera 0-0:soc_camera:
soc_camera_reqbufs: 1Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
1024, pixelformat = 'GREY'
mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_freecamera 0-0:soc_camera: mmap called, vma=0xc4f886e0 mx3-camera.0:videobuf_dma_contig:__videobuf_mmap_mappermx3-camera.0:videobuf_dma_contig:dma_alloc_coherentdata is at addr
c9000000Quoted 2 lines
Quoted 2 lines
(size 1572864)
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig: mmapc4fafec0: q=c8b6300440147000-402c7000
Quoted 8 lines
Quoted 8 lines
(180000) pgoff 00084000 buf 0
Quoted 1 line
mx3-camera.0:
videobuf_dma_contig:vm_openc4fafec0[count=0,vma=40147000-402c7000]
Quoted 5 lines
camera 0-0:
soc_camera: vma start=0x40147000, size=1572864, ret=0 mx3-camera.0:videobuf_dma_contig:__videobuf_iolockmemory method MMAP camera 0-0:soc_camera:soc_camera_streamonsixcam_start_capture(): trigger on!
ipu-core:ipu_idmac: write param mem - addr =0x00010070, data =
0x00000000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010071, data =
0x00004000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010072, data =
0x00000000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010073, data =
0xFF5FF000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010074, data =
0x00000003Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010078, data =
0x84000000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x00010079, data =
0x00000000Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x0001007A, data =
0x3E0E2FFBQuoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x0001007B, data =
0x00000002Quoted 1 line
Quoted 1 line
Quoted 1 line
ipu-core:
ipu_idmac: write param mem - addr =0x0001007C, data =
0x00000000Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
dma dma0chan7:
ipu_idmac: Submitting sgc4e0772c
dma dma0chan7:ipu_idmac: Updated sgc4e0772con channel0x7buffer 0
ipu-core:ipu_idmac:IDMAC_CONF0x70,IC_CONF0x0,IDMAC_CHA_EN0x0,
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE
0x0,Quoted 2 lines
Quoted 2 lines
TASKS_STAT0x3Quoted 1 line
ipu-core:
ipu_idmac:IDMAC_CONF0x70,IC_CONF0x40000001,IDMAC_CHA_EN
0x80,Quoted 2 lines
Quoted 2 lines
IDMAC_CHA_PRI0x80,IDMAC_CHA_BUSY0x0Quoted 1 line
ipu-core:
ipu_idmac:BUF0_RDY0x80,BUF1_RDY0x0,CUR_BUF0x0,DB_MODE
0x0,Quoted 4 lines
Quoted 4 lines
TASKS_STAT0x3Quoted 3 lines
camera 0-0:
mx3_camera: Submitted cookie 2 DMA0x84000000dma dma0chan7:ipu_idmac: IDMAC irq 176, buf 0
dma dma0chan7:ipu_idmac: IRQ on active buffer on channel 7, active 0,ready
Quoted 18 lines
Quoted 18 lines
0, 0, current 0!
Quoted 5 lines
[ ten seconds pass, and a lot of frames come out of my camera ]
capture: Select timeout. Exiting... mx3-camera.0:
videobuf_dma_contig:vm_closec4fafec0[count=1,vma=40147000-402c7000]
Quoted 2 lines
mx3-camera.0:
videobuf_dma_contig: munmapc4fafec0q=c8b63004 camera 0-0:mx3_camera: Release active DMA0x84000000(state 3), queue notempty
Quoted 7 lines
camera 0-0:
mx3_camera:free_buffer(vb=0xc4e076c0)0x401470001572864 mx3-camera.0:videobuf_dma_contig: buf[0] freeingc9000000
ipu-core:ipu_idmac: timeout = 0 * 10mssixcam_release(): ok
camera 0-0: MX3 Camera driver detached from camera 0
camera 0-0:soc_camera: camera device closeQuoted 3 lines
Quoted 3 lines
Quoted 3 lines
Any clue?
BTW, this dump shows a few apparently unneeded calls to camera
set_fmt()and
Quoted 1 line
Quoted 1 line
get_bus_params().---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/