public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 23 Jan 2014 00:13:01 +0100	[thread overview]
Message-ID: <52E0507D.1060103@xs4all.nl> (raw)
In-Reply-To: <2270106.dN7Lhra68Q@avalon>

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.

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.

Regards,

	Hans

On 01/22/2014 11:55 PM, Laurent Pinchart wrote:
> Hi Hans and Detlev,
> 
> While reviewed driver code that models the hardware using the media 
> controller, I noticed a patch that enabled subdev controls inheritance for the 
> video nodes. While this is useful for fixed devices, the complexity, 
> genericity and flexibility of the hardware at hand makes this undesirable, 
> given that we can't guarantee that a control won't be instantiated more than 
> once in the pipeline.
> 
> I've thus asked what triggered the need for controls inheritance, and found 
> out that the developers wanted to use qv4l2 as a demo application 
> (congratulations to Hans for such a useful application :-)). As qv4l2 doesn't 
> support subdevices, accessing controls required inheriting them on video 
> nodes.
> 
> There's an existing GUI test application for media controller-based devices 
> called mci (https://gitorious.org/mci) but it hasn't been maintained for quite 
> some time, and isn't as feature-complete as qv4l2. I was thus wondering 
> whether it would make sense to add explicit media controller support to qv4l2, 
> or whether the two applications should remain separate (in the later case some 
> code could probably still be shared).
> 
> Any opinion and/or desire to work on this ?
> 


  reply	other threads:[~2014-01-22 23:13 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 [this message]
2014-01-24 13:08   ` Laurent Pinchart
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=52E0507D.1060103@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