Home
last modified time | relevance | path

Searched +full:2592 +full:x1944 (Results 1 – 10 of 10) sorted by relevance

/openbmc/linux/Documentation/admin-guide/media/
H A Dipu3.rst88 2592x1944 image capture.
105 media-ctl -d $MDEV -V "ov5670:0 [fmt:SGRBG10/2592x1944]"
106 media-ctl -d $MDEV -V "ipu3-csi2 0:0 [fmt:SGRBG10/2592x1944]"
107 media-ctl -d $MDEV -V "ipu3-csi2 0:1 [fmt:SGRBG10/2592x1944]"
129 With the above command, 10 frames are captured at 2592x1944 resolution, with
363 For the ov5670 example, for an input frame with a resolution of 2592x1944
365 for input feeder, BDS and GDC are 2592x1944, 2592x1944 and 2560x1920
371 For an image captured with 2592x1944 [#f4]_ resolution, with desired output
380 --fmt=type:VIDEO_OUTPUT_MPLANE,width=2592,height=1944,pixelformat=0X47337069 \
/openbmc/linux/Documentation/devicetree/bindings/media/i2c/
H A Dovti,ov5675.yaml18 image sensor that delivers 2592x1944 at 30fps. It provides full-frame,
H A Dovti,ov5693.yaml15 image sensors that deliver 2592x1944 at 30fps. It provides full-frame,
/openbmc/linux/Documentation/devicetree/bindings/media/
H A Dvideo-interface-devices.yaml40 A typical example for a sensor with a 2592x1944 pixel array matrix
/openbmc/linux/drivers/staging/media/atomisp/i2c/ov5693/
H A Dov5693.h541 *DS from 2592x1952
957 * 2592x1944 30fps 0.6ms VBlanking 2lane 10Bit
1189 .width = 2592,
1200 .width = 2592,
1304 .width = 2592,
1315 .width = 2592,
/openbmc/linux/drivers/media/i2c/
H A Dov5647.c73 #define OV5647_PIXEL_ARRAY_WIDTH 2592U
508 /* 2592x1944 full resolution full FOV 10-bit mode. */
514 .width = 2592,
520 .width = 2592,
562 .width = 2592,
H A Dar0521.c37 #define AR0521_WIDTH_MAX 2592u
625 /* Initialize blanking limits using the default 2592x1944 format. */ in ar0521_init_controls()
H A Dov5648.c707 /* 2592x1944 */
712 .output_size_x = 2592,
H A Dov5640.c37 #define OV5640_PIXEL_ARRAY_WIDTH 2592
1094 /* 2592x1944 */
1110 .width = 2592,
1127 .width = 2592,
H A Dov5670.c1777 * 4:3 ==> {2592x1944, 1296x972, 648x486}
1782 .width = 2592,