Lines Matching full:sink

191 -  Formats should be propagated from sink pads to source pads. Modifying
192    a format on a source pad should not modify the format on any sink
196    reset the scale factors to default values when sink pads formats are
198    source pads formats should be reset to the sink pads formats.
255     * - Configure frontend sink format
268     * - Configure scaler sink format
285     * - Configure scaler sink compose selection
309    host frontend and scaler sink and source pads have the default
310    values, as well as the compose rectangle on the scaler's sink pad.
312 2. The application configures the frontend sink pad format's size to
316 3. The application configures the scaler sink pad format's size to
319    on the sink pad is set to V4L2_MBUS_FMT_SGRBG_1X8. The driver
321    scaler's sink pad, and the format to the scaler source pad.
324    rectangle of the scaler's sink pad 1280x960. The driver propagates
356 On sink pads, cropping is applied relative to the current pad format.
368 rectangle on the subdev's sink pad is scaled to the size configured
375 On source pads, cropping is similar to sink pads, with the exception
377 COMPOSE rectangle on the sink pad. In both sink and source pads, the
415 the sink pad towards the source pad. This is also reflected in the order
424 previous step. The exception to this rule is the sink compose
425 rectangle, which refers to the sink compose bounds rectangle --- if it
428 1. Sink pad format. The user configures the sink pad format. This format
432 2. Sink pad actual crop selection. The sink pad crop defines the crop
433    performed to the sink pad format.
435 3. Sink pad actual compose selection. The size of the sink pad compose
436    rectangle defines the scaling ratio compared to the size of the sink
438    the location of the actual sink compose rectangle in the sink compose
442    performed to the image in the sink compose bounds rectangle.
452 rectangle. For example, if sink crop is not supported, the compose
453 selection will refer to the sink pad format dimensions instead.
464 In the above example, the subdev supports cropping on its sink pad. To
465 configure it, the user sets the media bus format on the subdev's sink
466 pad. Now the actual crop rectangle can be set on the sink pad --- the
468 rectangle to be cropped from the sink format. The size of the sink crop
484 ignored in sink compose target. Both of the locations of the source crop
485 rectangles refer to the sink scaling rectangle, independently cropping
497 The subdev driver supports two sink pads and two source pads. The images
498 from both of the sink pads are individually cropped, then scaled and
523 link connecting a transmitter source pad with a sink pad on the receiver. For
527 sink pad. The stream-aware receiver will de-multiplex the streams received on
528 the its sink pad and allows to route them individually to one of its source
532 non-multiplexed subdev drivers. However, if the driver at the sink end of a link
534 There may be additional limitations specific to the sink device.
540 the media pipeline from a source (e.g. a sensor) towards the final sink (e.g. a
543 tables which describe how the incoming streams from sink pads are routed to the
565 Instead of the sub-device wide merging of streams from all sink pads
567 other. Any number of routes from streams on sink pads towards streams on
591 respect to routing. Typically any route between the sub-device's sink and source
618    associated with either sink or source pads of routes configured using the
629 - Multiplexer bridge (Bridge). The bridge has two sink pads, connected to the
632 - Receiver in the SoC (Receiver). The receiver has a single sink pad (pad 0),
654     * - Sink Pad/Stream
670     * - Sink Pad/Stream