From: "Zhang, Ning A" <ning.a.zhang@intel.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: "Zhang, Ning A" <ning.a.zhang@intel.com>
Subject: is it possible to use single IOCTL to setup media pipeline?
Date: Thu, 22 Nov 2018 02:51:48 +0000 [thread overview]
Message-ID: <1542855107.1288.32.camel@intel.com> (raw)
Hello everyone
when we need to setup media pipeline, eg, for camera capture, media-ctl
needs to be called multiple time to setup media link and subdev
formats, or similar code in a single application. this will use
multiple IOCTLs on "/dev/mediaX" and "/dev/v4l2-subdevY".
to setup media pipeline in userspace requires to fully understanding
the topology of the media stack. but the fact is only media driver
developer could know how to setup media pipeline. each time driver
updates, this would break userspace application if application
engineers don't know this change. In this case, if a IOCTL is designed
to setup media pipeline, no need to update applications, after driver
is updated.
this will not only benefit for design a single IOCTL, this also helps
to hide the detail of media pipeline, by load a binary blob which holds
information about how to setup pipeline, or hide it in bootloader/ACPI
tables/device tree, etc.
another benefit is save time for setup media pipeline, if there is a
PKI like "time for open camera". as my test, this will saves hundreds
of milliseconds.
is this acceptable?
BR.
Ning.
next reply other threads:[~2018-11-22 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 2:51 Zhang, Ning A [this message]
2018-11-22 7:06 ` is it possible to use single IOCTL to setup media pipeline? Tomasz Figa
2018-11-22 8:59 ` Zhang, Ning A
2018-11-22 13:46 ` Sakari Ailus
2018-11-22 13:56 ` Tomasz Figa
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=1542855107.1288.32.camel@intel.com \
--to=ning.a.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.