[PATCH 2/3] media: Documentation: v4l: LINK_FREQ can be an INTEGER64 control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



When a device passes through the video data while still having its own
receiver and transmitter, it can use the same frequency as the upstream
link does. The Intel MEI CSI device is an example of this. An integer menu
control isn't useful in conveying the actual frequency to the receiver in
this case.

Document that the LINK_FREQ control may also be a 64-bit integer control.

Signed-off-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx>
---
 .../userspace-api/media/v4l/ext-ctrls-image-process.rst         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
index b1c2ab2854af..7a3ccb100e1d 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
@@ -22,7 +22,7 @@ Image Process Control IDs
 
 .. _v4l2-cid-link-freq:
 
-``V4L2_CID_LINK_FREQ (integer menu)``
+``V4L2_CID_LINK_FREQ (integer menu or 64-bit integer)``
     The frequency of the data bus (e.g. parallel or CSI-2).
 
 .. _v4l2-cid-pixel-rate:
-- 
2.39.2





[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux