On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> 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.
Just to note that there is a pull request pending from me that
removes this from the cobalt driver. So once that's merged there
are only two drivers that do this.
Anyway:
Acked-by: Hans Verkuil <hans.verk...@cisco.com>
Regards,
Hans
>
> Signed-off-by: Mauro Carvalho Chehab <mche...@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 75ccc9d6614d..ed011ed123cc 100644
> --- a/Documentation/media/uapi/v4l/open.rst
> +++ b/Documentation/media/uapi/v4l/open.rst
> @@ -47,6 +47,13 @@ the periferal can be used. For such devices, the
> sub-devices' configuration
> can be controlled via the :ref:`sub-device API <subdev>`, which creates one
> device node per sub-device.
>
> +.. 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
