tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

media: Documentation: Additional streams generally don't harm capture

Having extra streams on the source end of the link that cannot be captured
by the sink sub-device generally are not an issue, at least not on CSI-2
bus. Still document that there may be hardware-specific limitations. For
example on parallel bus this might not work on all cases.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>

authored by

Sakari Ailus and committed by
Hans Verkuil 74491090 21828609

+3 -3
+3 -3
Documentation/userspace-api/media/v4l/dev-subdev.rst
··· 529 529 pads. 530 530 531 531 Subdevice drivers that support multiplexed streams are compatible with 532 - non-multiplexed subdev drivers, but, of course, require a routing configuration 533 - where the link between those two types of drivers contains only a single 534 - stream. 532 + non-multiplexed subdev drivers. However, if the driver at the sink end of a link 533 + does not support streams, then only stream 0 of source end may be captured. 534 + There may be additional limitations specific to the sink device. 535 535 536 536 Understanding streams 537 537 ^^^^^^^^^^^^^^^^^^^^^