Hi Biju,
On Tue, Feb 13, 2024 at 02:02:40PM +0000, Biju Das wrote:
> Since OV5645 is showing issues @400kHz, it makes sense to add a small
> delay after register writes for settling the register values. So introduce
> a small delay by adding a read() after write() and also add a debug code
> for data mismatch.
That looks not right to me. A write reg should succeed. If it doesn't,
then either the bus speed needs to be reduced on that board, or the
frequency should be measured (maybe the clock on the bus is too fast and
bigger than 400kHz?), or maybe the chip has issues so we need delays
here and there. Just printing debug output if there is a mismatch is
nothing for upstream as well, I'd say. It helps to find out after which
register writes we need delays, but this is only for development, no?
All the best,
Wolfram
>
> Signed-off-by: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
> ---
> drivers/media/i2c/ov5645.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/media/i2c/ov5645.c b/drivers/media/i2c/ov5645.c
> index a5cc959d535e..ea9b7c610f2d 100644
> --- a/drivers/media/i2c/ov5645.c
> +++ b/drivers/media/i2c/ov5645.c
> @@ -624,11 +624,20 @@ static int ov5645_set_register_array(struct ov5645 *ov5645,
> {
> unsigned int i;
> int ret;
> + u8 val;
>
> for (i = 0; i < num_settings; ++i, ++settings) {
> ret = ov5645_write_reg(ov5645, settings->reg, settings->val);
> if (ret < 0)
> return ret;
> +
> + ret = ov5645_read_reg(ov5645, settings->reg, &val);
> + if (ret < 0)
> + return ret;
> +
> + if (val != settings->val)
> + dev_dbg(ov5645->dev, "Data mismatch reg=%x val=%x/%x\n",
> + settings->reg, settings->val, val);
> }
>
> return 0;
> --
> 2.25.1
>
>
Attachment:
signature.asc
Description: PGP signature
