Lines Matching refs:streams
500 independent streams are cropped and sent out of the subdev from the
512 Simple V4L2 sub-devices do not support multiple, unrelated video streams,
516 two or compose two streams into one, but the inputs and outputs for the
519 Some hardware, e.g. MIPI CSI-2, support multiplexed streams, that is, multiple
520 data streams are transmitted on the same bus, which is represented by a media
522 example, a camera sensor can produce two distinct streams, a pixel stream and a
525 sink pad. The stream-aware receiver will de-multiplex the streams received on
529 Subdevice drivers that support multiplexed streams are compatible with
534 Understanding streams
540 streams from one end of the link to the other, and sub-devices have routing
541 tables which describe how the incoming streams from sink pads are routed to the
552 multiplexed streams the 'stream' field is always 0.
554 Interaction between routes, streams, formats and selections
557 The addition of streams to the V4L2 sub-device interface moves the sub-device
561 the same as without streams (see :ref:`format-propagation`).
563 Instead of the sub-device wide merging of streams from all sink pads
565 other. Any number of routes from streams on sink pads towards streams on
570 are independent of similar configurations on other streams. This is
573 Configuring streams
576 The configuration of the streams is done individually for each sub-device and
577 the validity of the streams between sub-devices is validated when the pipeline
580 There are three steps in configuring the streams:
597 Multiplexed streams setup example
606 sensors (pads 0, 1), and one source pad (pad 2), which outputs two streams.
610 engine. The receiver demultiplexes the incoming streams to the source pads.
662 selections for the streams. This is similar to performing this step without
663 streams, with just one exception: the ``stream`` field needs to be assigned