media: Clarify v4l2-async subdevice addition API
authorEzequiel Garcia <ezequiel@collabora.com>
Mon, 18 Jan 2021 01:52:55 +0000 (02:52 +0100)
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>
Sat, 6 Feb 2021 08:30:10 +0000 (09:30 +0100)
commit3e90e5ad9497d993852e638f75e9e154787bdd61
tree25e01837d5587f9386b3869d98582b24e4040cdb
parentb01edcbd409cf713ff4516c6e1e057834b4b43d6
media: Clarify v4l2-async subdevice addition API

Now that most users of v4l2_async_notifier_add_subdev have been converted,
let's fix the documentation so it's more clear how the v4l2-async API
should be used.

Document functions that drivers should use, and their purpose.

Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Helen Koike <helen.koike@collabora.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Documentation/driver-api/media/v4l2-subdev.rst
include/media/v4l2-async.h