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 <mche...@s-opensource.com>
Acked-by: Sakari Ailus <sakari.ai...@linux.intel.com>
Acked-by: Hans Verkuil <hans.verk...@cisco.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 58ab75959584..ccdf53ab347c 100644
--- a/Documentation/media/uapi/v4l/open.rst
+++ b/Documentation/media/uapi/v4l/open.rst
@@ -62,6 +62,13 @@ typically involves configuring the links using the **Media
controller**
interface and the media bus formats on pads (at both ends of the links)
using the **V4L2 sub-device** interface.
+.. note::
+
+ A **vdevnode-centric** may also 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.
+
+
.. attention::
Devices that require **MC-centric** media hardware control should
--
2.13.6
