[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z9AGxJuk7V-QPKW1@kekkonen.localdomain>
Date: Tue, 11 Mar 2025 09:47:48 +0000
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: shravan kumar <shravan.chippa@...rochip.com>
Cc: mchehab@...nel.org, kieran.bingham@...asonboard.com,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
conor.dooley@...rochip.com, valentina.fernandezalanis@...rochip.com,
praveen.kumar@...rochip.com
Subject: Re: [PATCH V7 2/4] media: i2c: imx334: common reg value correction
Hi Shravan,
On Wed, Mar 05, 2025 at 10:44:40AM +0530, shravan kumar wrote:
> From: Shravan Chippa <shravan.chippa@...rochip.com>
>
> correcting the CPWAIT_TIME value as per the data sheet
> for the link frequency and input clock
>
> Signed-off-by: Shravan Chippa <shravan.chippa@...rochip.com>
I've postponed applying this one once we have a better understanding what
that change actually is and why Tarang would seem to want to revert it.
> ---
> drivers/media/i2c/imx334.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
> index db61b298ceb3..0b42bc0470a1 100644
> --- a/drivers/media/i2c/imx334.c
> +++ b/drivers/media/i2c/imx334.c
> @@ -191,7 +191,7 @@ static const struct imx334_reg common_mode_regs[] = {
> {0x31a0, 0x20},
> {0x31a1, 0x0f},
> {0x300c, 0x3b},
> - {0x300d, 0x29},
> + {0x300d, 0x2a},
> {0x314c, 0x29},
> {0x314d, 0x01},
> {0x315a, 0x06},
--
Kind regards,
Sakari Ailus
Powered by blists - more mailing lists