Lines Matching refs:formats

37 -  negotiate image formats on individual pads
77 .. _pad-level-formats:
84     Pad-level formats are only applicable to very complex devices that
94 Image formats are typically negotiated on video capture and output
122 configured differently. Applications need to configure the formats at
130 negotiate formats on a per-pad basis.
134 formats. The pipeline is checked for formats mismatch at
147 Acceptable formats on pads can (and usually do) depend on a number of
148 external parameters, such as formats on other pads, active links, or
149 even controls. Finding a combination of formats on all pads in a video
151 formats enumeration only. A format negotiation mechanism is required.
158 a set of formats parameters that are not connected to the hardware
159 configuration. Modifying those 'try' formats leaves the device state
163 While not kept as part of the device state, try formats are stored in
182 (as long as external parameters, such as formats on other pads or links'
185 Drivers automatically propagate formats inside sub-devices. When a try
186 or active format is set on a pad, corresponding formats on other pads of
188 modify formats as required by the device. However, they should comply
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.
203 explicitly with compatible formats. Identical formats on the two ends of
205 different formats matching device requirements as being compatible.
326 formats by setting the ``which`` argument to
327 ``V4L2_SUBDEV_FORMAT_ACTIVE``. Active formats are changed exactly as try
328 formats by drivers. To avoid modifying the hardware state during format
329 negotiation, applications should negotiate try formats first and then
330 modify the active settings using the try formats returned during the
351 As for pad formats, drivers store try and active rectangles for the
503     subdev-formats