From: Julien BERAUD <julien.beraud@parrot.com>
To: <linux-media@vger.kernel.org>
Subject: Configurable Video Controller Driver
Date: Thu, 10 Jul 2014 16:19:06 +0200 [thread overview]
Message-ID: <53BEA0DA.9000706@parrot.com> (raw)
Hi,
We are developing a driver for our video controller which has the
particularity of being very reconfigurable.
We have reached a point at which the complexity and variety of the
applications we need to implement forces us to
design an api/library that allows us to configure the interconnection of
the different video processing units(Camera interfaces,
LCD interfaces, scalers, rotators, demosaicing, dead pixel correction,
etc...) from userland.
The media controller api has the limitation of not being able to create
links but just browsing and activating/deactivating them.
If we just allowed a user to activate/deactivate links, then we would
have to declare all the possible connections between
the different blocks, which would make it very confusing from a userland
point of view. Moreover, the interconnection constraints
would have to be dealt with very generically, which would make it very
difficult in the kernel too.
The conclusion we have reached yet is that we have to design an API that
allows us to create v4l2 subdevices that have certain
capabilities(scaling,rotating, demosaicing, etc...) and then to create
links between them from a userland library.
I would like to know if anything like this has been implemented yet or
if someone has been thinking about such an
architecture before.
Thanks for your inputs,
Julien BERAUD
next reply other threads:[~2014-07-10 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 14:19 Julien BERAUD [this message]
2014-07-21 11:14 ` Configurable Video Controller Driver Sakari Ailus
2014-07-31 8:53 ` Julien BERAUD
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=53BEA0DA.9000706@parrot.com \
--to=julien.beraud@parrot.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;
as well as URLs for NNTP newsgroup(s).