Searched refs:ov5670 (Results 1 – 5 of 5) sorted by relevance
| /Linux-v5.4/drivers/media/i2c/ |
| D | ov5670.c | 1814 struct ov5670 { struct
1836 #define to_ov5670(_sd) container_of(_sd, struct ov5670, sd) argument
1839 static int ov5670_read_reg(struct ov5670 *ov5670, u16 reg, unsigned int len, in ov5670_read_reg() argument
1842 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_read_reg()
1875 static int ov5670_write_reg(struct ov5670 *ov5670, u16 reg, unsigned int len, in ov5670_write_reg() argument
1878 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_write_reg()
1906 static int ov5670_write_regs(struct ov5670 *ov5670, in ov5670_write_regs() argument
1909 struct i2c_client *client = v4l2_get_subdevdata(&ov5670->sd); in ov5670_write_regs()
1914 ret = ov5670_write_reg(ov5670, regs[i].address, 1, regs[i].val); in ov5670_write_regs()
1928 static int ov5670_write_reg_list(struct ov5670 *ov5670, in ov5670_write_reg_list() argument
[all …]
|
| D | Makefile | 72 obj-$(CONFIG_VIDEO_OV5670) += ov5670.o
|
| D | Kconfig | 727 module will be called ov5670.
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | ipu3.rst | 86 Let us take the example of ov5670 sensor connected to CSI2 port 0, for a
89 Using the media contorller APIs, the ov5670 sensor is configured to send
96 # and that ov5670 sensor is connected to i2c bus 10 with address 0x36
98 export SDEV=$(media-ctl -d $MDEV -e "ov5670 10-0036")
101 media-ctl -d $MDEV -l "ov5670:0 -> ipu3-csi2 0:0[1]"
104 media-ctl -d $MDEV -V "ov5670:0 [fmt:SGRBG10/2592x1944]"
300 For the ov5670 example, for an input frame with a resolution of 2592x1944
|
| /Linux-v5.4/ |
| D | MAINTAINERS | 11995 F: drivers/media/i2c/ov5670.c
|
