From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
"Ravi, Deepthy" <deepthy.ravi@ti.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"g.liakhovetski@gmx.de" <g.liakhovetski@gmx.de>,
Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Subject: Re: [PATCH 4/8] ispvideo: Add support for G/S/ENUM_STD ioctl
Date: Wed, 28 Sep 2011 06:59:30 -0300 [thread overview]
Message-ID: <4E82F002.4040401@infradead.org> (raw)
In-Reply-To: <201109280041.29952.laurent.pinchart@ideasonboard.com>
Em 27-09-2011 19:41, Laurent Pinchart escreveu:
> Hi Mauro,
>
> On Wednesday 28 September 2011 00:31:32 Mauro Carvalho Chehab wrote:
>> Em 19-09-2011 12:31, Hiremath, Vaibhav escreveu:
>>> On Friday, September 16, 2011 6:36 PM Laurent Pinchart wrote: > >> On
> Friday 16 September 2011 15:00:53 Ravi, Deepthy wrote:
>>>>> On Thursday, September 08, 2011 10:51 PM Laurent Pinchart wrote:
>>>>>> On Thursday 08 September 2011 15:35:22 Deepthy Ravi wrote:
>>>>>>> From: Vaibhav Hiremath <hvaibhav@ti.com>
>>>>>>>
>>>>>>> In order to support TVP5146 (for that matter any video decoder),
>>>>>>> it is important to support G/S/ENUM_STD ioctl on /dev/videoX
>>>>>>> device node.
>>>>>>
>>>>>> Why so ? Shouldn't it be queried on the subdev output pad directly ?
>>>>>
>>>>> Because standard v4l2 application for analog devices will call these
>>>>> std ioctls on the streaming device node. So it's done on /dev/video to
>>>>> make the existing apllication work.
>>>>
>>>> Existing applications can't work with the OMAP3 ISP (and similar complex
>>>> embedded devices) without userspace support anyway, either in the form
>>>> of a GStreamer element or a libv4l plugin. I still believe that analog
>>>> video standard operations should be added to the subdev pad operations
>>>> and exposed through subdev device nodes, exactly as done with formats.
>>>
>>> I completely agree with your point that, existing application will not
>>> work without setting links properly. But I believe the assumption here
>>> is, media-controller should set the links (along with pad formants) and
>>> all existing application should work as is. Isn't it?
>>
>> Yes.
>>
>>> The way it is being done currently is, set the format at the pad level
>>> which is same as analog standard resolution and use existing application
>>> for streaming...
>>
>> Yes.
>>
>>> I am ok, if we add s/g/enum_std api support at sub-dev level but this
>>> should also be supported on streaming device node.
>>
>> Agreed. Standards selection should be done at device node, just like any
>> other device.
>
> No. Please see my reply to Vaibhav's e-mail. Standard selection should be done
> on the subdev pads, for the exact same reason why formats and selection
> rectangles are configured on subdev pads.
NACK. Let's not reinvent the wheel. the MC should not replace the V4L2 API.
Mauro.
next prev parent reply other threads:[~2011-09-28 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 13:35 [PATCH 4/8] ispvideo: Add support for G/S/ENUM_STD ioctl Deepthy Ravi
2011-09-08 17:21 ` Laurent Pinchart
2011-09-16 13:00 ` Ravi, Deepthy
2011-09-16 13:06 ` Laurent Pinchart
2011-09-19 15:31 ` Hiremath, Vaibhav
2011-09-27 18:06 ` Laurent Pinchart
2011-09-28 6:10 ` Hiremath, Vaibhav
2011-09-28 9:28 ` Sakari Ailus
2011-09-27 22:31 ` Mauro Carvalho Chehab
2011-09-27 22:41 ` Laurent Pinchart
2011-09-28 9:59 ` Mauro Carvalho Chehab [this message]
2011-09-28 10:03 ` Sakari Ailus
2011-09-28 13:29 ` Laurent Pinchart
2011-09-28 13:46 ` Hiremath, Vaibhav
2011-09-27 22:49 ` Gary Thomas
2011-09-28 9:58 ` Mauro Carvalho Chehab
2011-09-08 21:38 ` 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=4E82F002.4040401@infradead.org \
--to=mchehab@infradead.org \
--cc=deepthy.ravi@ti.com \
--cc=g.liakhovetski@gmx.de \
--cc=hvaibhav@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox