Lines Matching full:formats

30 -  negotiate image formats on individual pads
70 .. _pad-level-formats:
72 Pad-level Formats
77     Pad-level formats are only applicable to very complex devices that
87 Image formats are typically negotiated on video capture and output
115 configured differently. Applications need to configure the formats at
123 negotiate formats on a per-pad basis.
127 formats. The pipeline is checked for formats mismatch at
140 Acceptable formats on pads can (and usually do) depend on a number of
141 external parameters, such as formats on other pads, active links, or
142 even controls. Finding a combination of formats on all pads in a video
144 formats enumeration only. A format negotiation mechanism is required.
151 a set of formats parameters that are not connected to the hardware
152 configuration. Modifying those 'try' formats leaves the device state
156 While not kept as part of the device state, try formats are stored in
171 Formats returned by the driver during a negotiation iteration are
175 (as long as external parameters, such as formats on other pads or links'
178 Drivers automatically propagate formats inside sub-devices. When a try
179 or active format is set on a pad, corresponding formats on other pads of
181 modify formats as required by the device. However, they should comply
184 -  Formats should be propagated from sink pads to source pads. Modifying
189    reset the scale factors to default values when sink pads formats are
191    source pads formats should be reset to the sink pads formats.
193 Formats are not propagated across links, as that would involve
196 explicitly with compatible formats. Identical formats on the two ends of
198 different formats matching device requirements as being compatible.
259    size and V4L2_MBUS_FMT_SGRBG8_1X8 media bus code. Formats on the
279 formats by setting the ``which`` argument to
280 ``V4L2_SUBDEV_FORMAT_ACTIVE``. Active formats are changed exactly as try
281 formats by drivers. To avoid modifying the hardware state during format
282 negotiation, applications should negotiate try formats first and then
283 modify the active settings using the try formats returned during the
304 As for pad formats, drivers store try and active rectangles for the
456     subdev-formats