From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Michael Jones <michael.jones@matrix-vision.de>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Loïc Akue" <akue.loic@gmail.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Yordan Kamenov" <ykamenov@mm-sol.com>
Subject: Re: [PATCH] omap3isp: implement ENUM_FMT
Date: Wed, 23 Mar 2011 11:52:45 +0200 [thread overview]
Message-ID: <4D89C2ED.5080803@maxwell.research.nokia.com> (raw)
In-Reply-To: <4D889C61.905@matrix-vision.de>
Hi Michael,
Thanks for the patch.
Michael Jones wrote:
> From dccbd4a0a717ee72a3271075b1e3456a9c67ca0e Mon Sep 17 00:00:00 2001
> From: Michael Jones <michael.jones@matrix-vision.de>
> Date: Tue, 22 Mar 2011 11:47:22 +0100
> Subject: [PATCH] omap3isp: implement ENUM_FMT
>
> Whatever format is currently being delivered will be declared as the only
> possible format
>
> Signed-off-by: Michael Jones <michael.jones@matrix-vision.de>
> ---
>
> Some V4L2 apps require ENUM_FMT, which is a mandatory ioctl for V4L2.
> This patch doesn't enumerate all of the formats which could possibly be
> set (as is intended by ENUM_FMT), but at least it reports the one that
> is currently set.
What would be the purpose of ENUM_FMT in this case? It provides no
additional information to user space, and the information it provides is
in fact incomplete. Using other formats is possible, but that requires
changes to the format configuration on links.
As the relevant format configuration is done on the subdevs and not on
the video nodes, the format configuration on the video nodes is very
limited and much affected by the state of the formats on the subdev pads
(which I think is right). This is not limited to ENUM_FMT but all format
related IOCTLs on the OMAP 3 ISP driver.
My view is that should a generic application want to change (or
enumerate) the format(s) on a video node, the application would need to
be using libv4l for that.
A compatibility layer implemented in libv4l (plugin, not the main
library) needs to configure the links in the first place, so
implementing ENUM_FMT in the plugin would not be a big deal. It could
even provide useful information. The possible results of the ENUM_FMT
would also depend on what kind of pipeline configuration does the plugin
support, though.
(Cc Yordan and Hans.)
I discussed this with Laurent initially and the conclusion was that more
discussion is required. :-) Hans: do you have an opinion on this?
Best regards,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next prev parent reply other threads:[~2011-03-23 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 12:56 [PATCH] omap3isp: implement ENUM_FMT Michael Jones
2011-03-23 9:52 ` Sakari Ailus [this message]
2011-03-23 11:07 ` Michael Jones
2011-03-23 12:16 ` Laurent Pinchart
2011-03-24 7:28 ` Michael Jones
2011-03-24 7:42 ` Hans Verkuil
2011-03-24 8:13 ` Sakari Ailus
2011-03-24 10:36 ` Laurent Pinchart
2011-03-25 10:16 ` Michael Jones
2011-03-24 8:04 ` Sakari Ailus
2011-03-25 10:11 ` Michael Jones
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=4D89C2ED.5080803@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=akue.loic@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=michael.jones@matrix-vision.de \
--cc=ykamenov@mm-sol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox