Lines Matching full:formats

30 -  negotiate image formats on individual pads
75 .. _pad-level-formats:
77 Pad-level Formats
82     Pad-level formats are only applicable to very complex devices that
92 Image formats are typically negotiated on video capture and output
120 configured differently. Applications need to configure the formats at
128 negotiate formats on a per-pad basis.
132 formats. The pipeline is checked for formats mismatch at
145 Acceptable formats on pads can (and usually do) depend on a number of
146 external parameters, such as formats on other pads, active links, or
147 even controls. Finding a combination of formats on all pads in a video
149 formats enumeration only. A format negotiation mechanism is required.
156 a set of formats parameters that are not connected to the hardware
157 configuration. Modifying those 'try' formats leaves the device state
161 While not kept as part of the device state, try formats are stored in
176 Formats returned by the driver during a negotiation iteration are
180 (as long as external parameters, such as formats on other pads or links'
183 Drivers automatically propagate formats inside sub-devices. When a try
184 or active format is set on a pad, corresponding formats on other pads of
186 modify formats as required by the device. However, they should comply
189 -  Formats should be propagated from sink pads to source pads. Modifying
194    reset the scale factors to default values when sink pads formats are
196    source pads formats should be reset to the sink pads formats.
198 Formats are not propagated across links, as that would involve
201 explicitly with compatible formats. Identical formats on the two ends of
203 different formats matching device requirements as being compatible.
306    size and V4L2_MBUS_FMT_SGRBG8_1X8 media bus code. Formats on the
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