From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Detlev Casanova <detlev.casanova@gmail.com>,
linux-media@vger.kernel.org, hyun.kwon@xilinx.com
Subject: Re: qv4l2 and media controller support
Date: Fri, 24 Jan 2014 14:08:35 +0100 [thread overview]
Message-ID: <3336553.LUKAjLBShm@avalon> (raw)
In-Reply-To: <52E0507D.1060103@xs4all.nl>
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.
> 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 :-)
I've just posted a series of patches for libmediactl. Let's take it from
there.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-01-24 13:07 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 [this message]
2014-01-25 8:45 ` Hans Verkuil
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=3336553.LUKAjLBShm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=detlev.casanova@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=hyun.kwon@xilinx.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