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: Grabbing single stills on MX31 - Re: Solved? - Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c
Date: Mon, 11 May 2009 09:55:10 -0700 (PDT) [thread overview]
Message-ID: <951499.48393.qm@web32102.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0905071750050.9460@axis700.grange>
On Thu, 7 May 2009, Guennadi Liakhovetski wrote:
>
> On Thu, 7 May 2009, Agustin Ferrin Pozuelo wrote:
> > ...
> > I thought about the fact that I was only queuing one buffer, and that
> > this might be a corner case as sample code uses a lot of them. And that
> > in the older code that funny things could happen in the handler if we
> > ran out of buffers, though they didn't happen.
> >
> > So I have queued an extra buffer and voila, got it working.
> >
> > So thanks again!
> >
> > However, this could be a bug in ipu_idmac (or some other point), as
> > using a single buffer is very plausible, specially when grabbing huge
> > stills.
>
> Great, thanks for testing and debugging! Ok, so, I will have to test this
> case some time...
Guennadi,
This workaround (queuing 2 buffers when needing only one) is having the side effect of greatly increasing the time taken.
I did several tests playing with camera vertical blanking and looking at capture times:
Vblank / real / user / sys time:
0 / real 0m 0.90s / user 0m 0.00s / sys 0m 0.34s
1 frame / real 0m 1.04s / user 0m 0.00s / sys 0m 0.34s
2 frames / real 0m 1.18s / user 0m 0.00s / sys 0m 0.33s
2.5 (max)/ real 0m 1.23s / user 0m 0.00s / sys 0m 0.35s
I think the second frame is being captured altogether, and its dma transfer is not allowing any other process to run meanwhile. (VIDIOC_STREAMOFF is being called as soon as the first buffer is ready.)
Do you think it will be too hard to fix?
Regards,
--Agustín.
next prev parent reply other threads:[~2009-05-11 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 15:41 Solved? - Re: soc-camera: timing out during capture - Re: Testing latest mx3_camera.c Agustin Ferrin Pozuelo
2009-05-07 15:54 ` Guennadi Liakhovetski
2009-05-11 16:55 ` Agustin [this message]
2009-05-12 9:16 ` [PATCH] dma: fix ipu_idmac.c to not discard the last queued buffer Guennadi Liakhovetski
2009-05-12 12:14 ` Agustin
2009-05-12 18:31 ` Dan Williams
2009-05-16 16:46 ` Russell King - ARM Linux
2009-05-16 18:22 ` Guennadi Liakhovetski
2009-05-16 18:50 ` Russell King - ARM Linux
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=951499.48393.qm@web32102.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.