Home
last modified time | relevance | path

Searched refs:ov5670 (Results 1 – 6 of 6) sorted by relevance

/Linux-v6.1/drivers/media/i2c/
Dov5670.c1816 struct ov5670 { struct
1840 #define to_ov5670(_sd) container_of(_sd, struct ov5670, sd) argument
1843 static int ov5670_read_reg(struct ov5670 *ov5670, u16 reg, unsigned int len, in ov5670_read_reg() argument
1846 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_read_reg()
1879 static int ov5670_write_reg(struct ov5670 *ov5670, u16 reg, unsigned int len, in ov5670_write_reg() argument
1882 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_write_reg()
1910 static int ov5670_write_regs(struct ov5670 *ov5670, in ov5670_write_regs() argument
1913 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_write_regs()
1918 ret = ov5670_write_reg(ov5670, regs[i].address, 1, regs[i].val); in ov5670_write_regs()
1932 static int ov5670_write_reg_list(struct ov5670 *ov5670, in ov5670_write_reg_list() argument
[all …]
DMakefile86 obj-$(CONFIG_VIDEO_OV5670) += ov5670.o
DKconfig510 module will be called ov5670.
/Linux-v6.1/Documentation/admin-guide/media/
Dipu3.rst87 Let us take the example of ov5670 sensor connected to CSI2 port 0, for a
90 Using the media controller APIs, the ov5670 sensor is configured to send
98 # and that ov5670 sensor is connected to i2c bus 10 with address 0x36
99 export SDEV=$(media-ctl -d $MDEV -e "ov5670 10-0036")
102 media-ctl -d $MDEV -l "ov5670:0 -> ipu3-csi2 0:0[1]"
105 media-ctl -d $MDEV -V "ov5670:0 [fmt:SGRBG10/2592x1944]"
363 For the ov5670 example, for an input frame with a resolution of 2592x1944
Di2c-cardlist.rst95 ov5670 OmniVision OV5670 sensor
/Linux-v6.1/
DMAINTAINERS15245 F: drivers/media/i2c/ov5670.c