From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v3 7/7] media: open.rst: add a notice about subdev-API on vdev-centric
Date: Fri, 25 Aug 2017 12:11:57 -0300 [thread overview]
Message-ID: <141468a790ecffd1d5cf53a0985ef266ea70077d.1503673702.git.mchehab@s-opensource.com> (raw)
In-Reply-To: <cover.1503673702.git.mchehab@s-opensource.com>
In-Reply-To: <cover.1503673702.git.mchehab@s-opensource.com>
The documentation doesn't mention if vdev-centric hardware
control would have subdev API or not.
Add a notice about that, reflecting the current status, where
three drivers use it, in order to support some subdev-specific
controls.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
Documentation/media/uapi/v4l/open.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/media/uapi/v4l/open.rst b/Documentation/media/uapi/v4l/open.rst
index 3257a0527ac9..547d191dcef2 100644
--- a/Documentation/media/uapi/v4l/open.rst
+++ b/Documentation/media/uapi/v4l/open.rst
@@ -43,6 +43,13 @@ the application to know with device nodes are available
For **MC-centric** hardware peripheral control, before using the
peripheral, it is required to set the pipelines via the
+.. note::
+
+ A **vdev-centric** may optionally expose V4L2 sub-devices via
+ :ref:`sub-device API <subdev>`. In that case, it has to implement
+ the :ref:`media controller API <media_controller>` as well.
+
+
:ref:`media controller API <media_controller>`. For those devices, the
sub-devices' configuration can be controlled via the
:ref:`sub-device API <subdev>`, whith creates one device node
--
2.13.3
prev parent reply other threads:[~2017-08-25 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 15:11 [PATCH v3 0/7] document types of hardware control for V4L2 Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 2/7] media: open.rst: better document device node naming Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 3/7] media: open.rst: remove the minor number range Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 4/7] media: open.rst: document devnode-centric and mc-centric types Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 5/7] media: open.rst: Adjust some terms to match the glossary Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 6/7] media: videodev2: add a flag for MC-centric devices Mauro Carvalho Chehab
2017-08-25 15:11 ` Mauro Carvalho Chehab [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=141468a790ecffd1d5cf53a0985ef266ea70077d.1503673702.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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).