From: Hans Verkuil <hverkuil@xs4all.nl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Detlev Casanova <detlev.casanova@gmail.com>,
linux-media@vger.kernel.org, hyun.kwon@xilinx.com
Subject: Re: qv4l2 and media controller support
Date: Sat, 25 Jan 2014 09:45:00 +0100 [thread overview]
Message-ID: <52E3798C.6090407@xs4all.nl> (raw)
In-Reply-To: <3336553.LUKAjLBShm@avalon>
Hi Laurent,
On 01/24/2014 02:08 PM, Laurent Pinchart wrote:
> Hi Hans,
>
> On Thursday 23 January 2014 00:13:01 Hans Verkuil wrote:
>> Hi Laurent,
>>
>> First, regarding the inheritance of subdev controls: I found it annoying as
>> well that there is no way to do this. If you have a simple video pipeline,
>> then having to create subdev nodes just to set a few controls is unnecessary
>> complex. I've been thinking of adding a flag to the control handler that,
>> when set, will 'import' the private controls. The bridge driver is the one
>> that sets this as that is the only one that knows whether or not it is in
>> fact a simple pipeline.
>
> In my case the pipeline is potentially complex, given that it's implemented in
> an FPGA. The bridge driver just parses the DT pipeline representation and
> binds subdevs together. It has no concept of simple or complex pipelines. I've
> thus decided to go for an MC model, even for simple pipelines.
That makes a lot of sense. I was talking about e.g. PCI cards with a simple
video capture pipeline where this would actually be useful.
>> Secondly, I'd love to add MC support to qv4l2. But I'm waiting for you to
>> merge the MC library into v4l-utils.git. It's basically the reason why I
>> haven't looked at this at all.
>
> I assume that's a hint :-)
A big one :-)
>
> I've just posted a series of patches for libmediactl. Let's take it from
> there.
Thanks!
Hans
prev parent reply other threads:[~2014-01-25 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 22:55 qv4l2 and media controller support Laurent Pinchart
2014-01-22 23:13 ` Hans Verkuil
2014-01-24 13:08 ` Laurent Pinchart
2014-01-25 8:45 ` Hans Verkuil [this message]
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=52E3798C.6090407@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=detlev.casanova@gmail.com \
--cc=hyun.kwon@xilinx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox