Linux Media Controller development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Biju Das <biju.das.au@gmail.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] media: i2c: ov5645: Move the register 0x3008 from ov5645_global_init_setting
Date: Tue, 13 Feb 2024 23:27:21 +0100	[thread overview]
Message-ID: <ZcvsyRfVwC0aJ5fb@shikoro> (raw)
In-Reply-To: <20240213140240.159057-2-biju.das.jz@bp.renesas.com>

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

Hi Biju,

I couldn't find a datasheet for the OV5645 but the one for OV5642 looked
pretty similar when it comes to the issues mentioned here.

> Testing OV5645 with i2c bus frequency @400kHz on RZ/G2L SMARC EVL platform
> shows issues like the captured image is either greenish or it is not
> capturing the image at all. However, It is working ok when the i2c
> frequency is 100kHz. From this, it is clear that we have a timing issue
> at high speed. The testing also shows that if we add a delay >= 1 msec

That could match the "VDD stable to sensor stable" delay in the
datasheet.

> after register write {0x3008, 0x82}, then the captured image is always
> good. So, move the register 0x3008 and 0x3103 from ov5645_*_init_setting
> to a new table ov5645_global_init_setting.
> 
> Drop the unnecessary entry { 0x3008, 0x42 } from ov5645_*init_setting
> table at the start.

It seems this is not needed to fix your issue? Then, this would be a
seperate change with a dedicated reason, I'd think. There is another
pair of activating power-down mode and immediately disabling it again.
Either we simplify it, too, or we leave both in place. Or at least make
sure there wasn't a reason for them. I'd just leave them.

Rest looks good to me.

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-13 22:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 14:02 [PATCH 0/2] Fix OV5645 capture issue with 400kHz i2c bus frequency Biju Das
2024-02-13 14:02 ` [PATCH 1/2] media: i2c: ov5645: Move the register 0x3008 from ov5645_global_init_setting Biju Das
2024-02-13 22:27   ` Wolfram Sang [this message]
2024-02-14  7:44     ` Biju Das
2024-02-14  8:31       ` Wolfram Sang
2024-02-14 20:25         ` Biju Das
2024-02-14 20:49           ` Sakari Ailus
2024-02-14 20:54             ` Biju Das
2024-02-14 20:57               ` Biju Das
2024-02-14 23:34                 ` Kieran Bingham
2024-02-13 14:02 ` [PATCH 2/2] media: i2c: ov5645: Add a small delay after writes in ov5645_set_register_array() Biju Das
2024-02-13 22:32   ` Wolfram Sang
2024-02-14 20:30     ` Biju Das

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=ZcvsyRfVwC0aJ5fb@shikoro \
    --to=wsa@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=sakari.ailus@linux.intel.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