From: Michael Jones <michael.jones@matrix-vision.de>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: laurent.pinchart@ideasonboard.com,
"sakari.ailus@maxwell.research.nokia.com"
<sakari.ailus@maxwell.research.nokia.com>
Subject: controls, subdevs, and media framework
Date: Tue, 26 Oct 2010 17:08:12 +0200 [thread overview]
Message-ID: <4CC6EEDC.20206@matrix-vision.de> (raw)
I'm trying to understand how the media framework and V4L2 share the responsibility of configuring a video device. Referring to the ISP code on Laurent's media-0004-omap3isp branch, the video device is now split up into several devices... suppose you have a sensor delivering raw bayer data to the CCDC. I could get this raw data from the /dev/video2 device (named "OMAP3 ISP CCDC output") or I could get YUV data from the previewer or resizer. But I would no longer have a single device where I could ENUM_FMT and see that I could get either. Correct?
Having settled on a particular video device, (how) do regular controls (ie. VIDIOC_[S|G]_CTRL) work? I don't see any support for them in ispvideo.c. Is it just yet to be implemented? Or is it expected that the application will access the subdevs individually?
Basically the same Q for CROPCAP: isp_video_cropcap passes it on to the last link in the chain, but none of the subdevs in the ISP currently have a cropcap function implemented (yet). Does this still need to be written?
--
Michael Jones
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next reply other threads:[~2010-10-26 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 15:08 Michael Jones [this message]
2010-10-26 22:12 ` controls, subdevs, and media framework Laurent Pinchart
2010-10-27 13:48 ` Sakari Ailus
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=4CC6EEDC.20206@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.com \
/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.