From: Sakari Ailus Date: Mon, 16 Dec 2024 08:26:22 +0000 (+0200) Subject: media: Documentation: Receiver drivers should call v4l2_get_link_freq() X-Git-Tag: v6.15-rc1~174^2~158 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=015853f0bd274b5406934c239bd812a00fac11cc;p=linux.git media: Documentation: Receiver drivers should call v4l2_get_link_freq() Document that receiver drivers should call v4l2_get_link_freq() to obtain the link frequency. Signed-off-by: Sakari Ailus Reviewed-by: Tomi Valkeinen Signed-off-by: Hans Verkuil --- diff --git a/Documentation/driver-api/media/tx-rx.rst b/Documentation/driver-api/media/tx-rx.rst index 03768e5aa88f..0b8c9cde8ee4 100644 --- a/Documentation/driver-api/media/tx-rx.rst +++ b/Documentation/driver-api/media/tx-rx.rst @@ -53,6 +53,9 @@ Drivers that do not have user-configurable link frequency should report it through the ``.get_mbus_config()`` subdev pad operation, in the ``link_freq`` field of struct v4l2_mbus_config, instead of through controls. +Receiver drivers should use :c:func:`v4l2_get_link_freq` helper to obtain the +link frequency from the transmitter sub-device. + ``.enable_streams()`` and ``.disable_streams()`` callbacks ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^