[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250228103332.3647098-3-shravan.chippa@microchip.com>
Date: Fri, 28 Feb 2025 16:03:31 +0530
From: shravan kumar <shravan.chippa@...rochip.com>
To: <sakari.ailus@...ux.intel.com>, <mchehab@...nel.org>
CC: <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>,
<shravan.chippa@...rochip.com>
Subject: [PATCH V6 2/3] media: i2c: imx334: update mode_3840x2160_regs array
From: Shravan Chippa <shravan.chippa@...rochip.com>
The 3840x2160 mode operates with the imx334 reset values.
If we switch to other modes and then return to the 3840x2160 mode,
it should function correctly. so updated the mode_3840x2160_regs
array with the imx334 reset values.
Signed-off-by: Shravan Chippa <shravan.chippa@...rochip.com>
---
drivers/media/i2c/imx334.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/i2c/imx334.c b/drivers/media/i2c/imx334.c
index a800f2203592..f80a8ce8f9c5 100644
--- a/drivers/media/i2c/imx334.c
+++ b/drivers/media/i2c/imx334.c
@@ -344,6 +344,12 @@ static const struct imx334_reg mode_3840x2160_regs[] = {
{0x302d, 0x00},
{0x302e, 0x00},
{0x302f, 0x0f},
+ {0x3074, 0xb0},
+ {0x3075, 0x00},
+ {0x308e, 0xb1},
+ {0x308f, 0x00},
+ {0x30d8, 0x20},
+ {0x30d9, 0x12},
{0x3076, 0x70},
{0x3077, 0x08},
{0x3090, 0x70},
--
2.34.1
Powered by blists - more mailing lists