media: Documentation: v4l: Document sub-device notifiers
Document that sub-device notifiers are now registered using v4l2_async_subdev_nf_init(). No documentation is changed as it seems that sub-device notifiers were not documented apart from kernel-doc comments. Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Tested-by: Philipp Zabel <p.zabel@pengutronix.de> # imx6qp Tested-by: Niklas Söderlund <niklas.soderlund@ragnatech.se> # rcar + adv746x Tested-by: Aishwarya Kothari <aishwarya.kothari@toradex.com> # Apalis i.MX6Q with TC358743 Tested-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> # Renesas RZ/G2L SMARC Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
This commit is contained in:
parent
b8ec754ae4
commit
99939beaef
@ -218,6 +218,17 @@ available. There may be one or more async connections to a given sub-device but
|
||||
this is not known at the time of adding the connections to the notifier. Async
|
||||
connections are bound as matching async sub-devices are found, one by one.
|
||||
|
||||
Asynchronous sub-device notifier for sub-devices
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
A driver that registers an asynchronous sub-device may also register an
|
||||
asynchronous notifier. This is called an asynchronous sub-device notifier andthe
|
||||
process is similar to that of a bridge driver apart from that the notifier is
|
||||
initialised using :c:func:`v4l2_async_subdev_nf_init` instead. A sub-device
|
||||
notifier may complete only after the V4L2 device becomes available, i.e. there's
|
||||
a path via async sub-devices and notifiers to a notifier that is not an
|
||||
asynchronous sub-device notifier.
|
||||
|
||||
Asynchronous sub-device registration helper for camera sensor drivers
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user