From: Lane Brooks <lane@brooks.nu>
To: "laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Snapshot with the OMAP
Date: Sat, 28 Aug 2010 23:24:31 -0600 [thread overview]
Message-ID: <4C79EF0F.2090401@brooks.nu> (raw)
Laurent,
Suppose I am streaming 2048x1536 YUV images from a sensor into the OMAP.
I am piping it through the resizer to drop it to 640x480 for display. So
I am reading from /dev/video6 (resizer) and have the media bus links
setup appropriately. Now the user presses the shutter button. What is
the recommended way to read a single full resolution image?
It seems there are several options:
1. Reconfigure the media bus and read a single single full resolution
image out of the CCDC output on /dev/video2 and then
reconfigure it back to video mode.
2. Reconfigure the resizer to stop downsampling but instead output the
full resolution image for a single frame.
Do I need to stop the stream while doing either option?
These seem like clunky and slow options, though.
Is there a way to setup the media bus links so that I can actually have
handles to /dev/video2 and /dev/video6 open simultaneously? Then I can
normally read from /dev/video6 and then read single frames from
/dev/video2 whenever the user presses the shutter button?
I have noticed there is a some ISP_PIPELINE_STREAM_SINGLESHOT streaming
states in the isp code, but I don't what it is for or how to use it. Is
it related to my questions at all?
It gets even more complex if I want the streaming the video out of the
sensor at a lower resolution (for higher video rates) and want to change
the resolution of the sensor for the snapshot.
Thanks,
Lane
next reply other threads:[~2010-08-29 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 5:24 Lane Brooks [this message]
2010-08-30 7:53 ` Snapshot with the OMAP 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=4C79EF0F.2090401@brooks.nu \
--to=lane@brooks.nu \
--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.