[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191011103902.3145-1-wuxy@bitland.com.cn>
Date: Fri, 11 Oct 2019 18:39:02 +0800
From: wuxy@...land.com.cn
To: mchehab@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
dongchun.zhu@...iatek.corp-partner.google.com, tfiga@...gle.com,
drinkcat@...gle.com, wuxy <wuxy@...land.corp-partner.google.com>
Subject: [PATCH] media: ov5695: enable vsync pin output
From: wuxy <wuxy@...land.corp-partner.google.com>
For Kukui project, the ov5695 vsync signal needs to
be set to output,from ov5695 datasheet,the related
register control methods as follows:
0x3002 Bit[7] FISIN/VSYNC output enable
0x3010 Bit[7] enable FISIN/VSYNC as GPIO controlled by register
0x3008 Bit[7] register control FISIN/VSYNC output
TEST= boot to shell
Signed-off-by: Xingyu Wu <wuxy@...land.corp-partner.google.com>
---
drivers/media/i2c/ov5695.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/i2c/ov5695.c b/drivers/media/i2c/ov5695.c
index 34b7046d9702..71f0eae6037b 100644
--- a/drivers/media/i2c/ov5695.c
+++ b/drivers/media/i2c/ov5695.c
@@ -300,6 +300,9 @@ static const struct regval ov5695_global_regs[] = {
* mipi_datarate per lane 840Mbps
*/
static const struct regval ov5695_2592x1944_regs[] = {
+ {0x3002, 0x80},
+ {0x3008, 0x80},
+ {0x3010, 0x80},
{0x3501, 0x7e},
{0x366e, 0x18},
{0x3800, 0x00},
--
2.17.1
Powered by blists - more mailing lists