From: Michael Jones <michael.jones@matrix-vision.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media ML <linux-media@vger.kernel.org>
Subject: double-buffering with the omap3 parallel interface
Date: Wed, 12 Jun 2013 18:16:26 +0200 [thread overview]
Message-ID: <51B89EDA.90107@matrix-vision.de> (raw)
Hi Laurent & co.,
I'd like to look at what the maximum possible frame rates are for a
sensor connected to the OMAP3 ISP CCDC via the parallel interface,
writing frames directly to memory. I understand that there is some
minimum amount of time required between frames to pass on the finished
frame and set up the address to be written to for the next frame. From
the manual it looks like a double buffering scheme would've been
available on a different sensor interface, but isn't on the parallel one.
Do I see that right? Is it impossible to use double buffering of any
sort while using the parallel interface to memory?
I'm still using an older version of the driver, but I've browsed the
current state of the code, too. What behavior do you expect if the time
between frames is too short for the buffer management? Can it be
recovered from? Has this behavior changed in recent versions?
I see from the ISP block diagram that the "circular buffer" is between
the SBL and the MMU. Could this maybe be used to help the situation?
It seems to currently not be used at all along this path.
thanks,
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier
next reply other threads:[~2013-06-12 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 16:16 Michael Jones [this message]
2013-06-16 23:44 ` double-buffering with the omap3 parallel interface Sakari Ailus
2013-06-18 15:18 ` Laurent Pinchart
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=51B89EDA.90107@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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.