linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wuxy@bitland.com.cn
To: mchehab@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	dongchun.zhu@mediatek.corp-partner.google.com, tfiga@google.com,
	drinkcat@google.com, wuxy <wuxy@bitland.corp-partner.google.com>
Subject: [PATCH] media: ov5695: enable vsync pin output
Date: Fri, 11 Oct 2019 18:39:02 +0800	[thread overview]
Message-ID: <20191011103902.3145-1-wuxy@bitland.com.cn> (raw)

From: wuxy <wuxy@bitland.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@bitland.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




             reply	other threads:[~2019-10-11 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 10:39 wuxy [this message]
2019-10-17 10:40 ` [PATCH] media: ov5695: enable vsync pin output Tomasz Figa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191011103902.3145-1-wuxy@bitland.com.cn \
    --to=wuxy@bitland.com.cn \
    --cc=dongchun.zhu@mediatek.corp-partner.google.com \
    --cc=drinkcat@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tfiga@google.com \
    --cc=wuxy@bitland.corp-partner.google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).