From: Agustin <gatoguan-os@yahoo.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Date: Tue, 5 May 2009 05:53:28 -0700 (PDT) [thread overview]
Message-ID: <320049.73706.qm@web32101.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0905051412520.4568@axis700.grange>
On Tue, 5 May 2009, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
>
> On Tue, 5 May 2009, Agustin wrote:
>
> >
> > Hi Guennadi,
> >
> > --- Guennadi Liakhovetski wrote:
> > > On Mon, 13 Apr 2009, Agustin wrote:
> > >
> > > > 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 from git://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.
>
> Have you applied this patch:
>
> Author: Ming Lei
> 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.
>
> Signed-off-by: Ming Lei
> Reported-by: Guennadi Liakhovetski
> Signed-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...
> >
> > 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_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 19523897
> > sixcam_init(): initialized camera.
> > camera 0-0: MX3 Camera driver attached to camera 0
> > camera 0-0: soc_camera: camera device open
> > sixcam_set_fmt(): 640x480+0+0
> > sixcam_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 176
> > sixcam_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: 0x2095
> > sixcam_set_bus_param(): 0x2095
> > mx3-camera.0: mx3_camera: Set SENS_CONF to 708
> > VIDIOC_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_streamon
> > sixcam_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 * 10ms
> > sixcam_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
> >
>
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
next prev parent reply other threads:[~2009-05-05 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 17:28 Testing latest mx3_camera.c Agustin
2009-04-13 19:39 ` Guennadi Liakhovetski
2009-05-05 11:50 ` soc-camera: timing out during capture - " Agustin
2009-05-05 12:13 ` Guennadi Liakhovetski
2009-05-05 12:53 ` Agustin [this message]
2009-05-05 14:00 ` Guennadi Liakhovetski
2009-05-07 14:06 ` Agustin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=320049.73706.qm@web32101.mail.mud.yahoo.com \
--to=gatoguan-os@yahoo.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-media@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.