From: shravan kumar <shravan.chippa@microchip.com>
To: <sakari.ailus@linux.intel.com>, <mchehab@kernel.org>
Cc: <kieran.bingham@ideasonboard.com>, <linux-media@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <conor.dooley@microchip.com>,
<valentina.fernandezalanis@microchip.com>,
<praveen.kumar@microchip.com>, <shravan.chippa@microchip.com>
Subject: [PATCH V7 3/4] media: i2c: imx334: update mode_3840x2160_regs array
Date: Wed, 5 Mar 2025 10:44:41 +0530 [thread overview]
Message-ID: <20250305051442.3716817-4-shravan.chippa@microchip.com> (raw)
In-Reply-To: <20250305051442.3716817-1-shravan.chippa@microchip.com>
From: Shravan Chippa <shravan.chippa@microchip.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@microchip.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 0b42bc0470a1..a7c0bd38c9b8 100644
--- a/drivers/media/i2c/imx334.c
+++ b/drivers/media/i2c/imx334.c
@@ -343,6 +343,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
next prev parent reply other threads:[~2025-03-05 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 5:14 [PATCH V7 0/4] media: i2c: imx334: Add support for 1280x720 & 640x480 resolutions shravan kumar
2025-03-05 5:14 ` [PATCH V7 1/4] media: i2c: imx334: Optimized 4k and 2k mode register arrays shravan kumar
2025-03-05 5:14 ` [PATCH V7 2/4] media: i2c: imx334: common reg value correction shravan kumar
2025-03-11 9:47 ` Sakari Ailus
2025-03-11 10:09 ` Tarang Raval
2025-03-05 5:14 ` shravan kumar [this message]
2025-03-05 5:14 ` [PATCH V7 4/4] media: i2c: imx334: add modes for 720p and 480p resolutions shravan kumar
2025-03-05 9:35 ` Kieran Bingham
2025-03-05 10:22 ` Shravan.Chippa
2025-03-05 10:40 ` Tarang Raval
2025-03-05 10:49 ` Kieran Bingham
2025-03-05 11:30 ` Tarang Raval
2025-03-05 12:09 ` Kieran Bingham
2025-03-05 10:45 ` Kieran Bingham
2025-03-05 11:50 ` Sakari Ailus
2025-03-05 12:16 ` Kieran Bingham
2025-03-05 12:59 ` Dave Stevenson
2025-03-06 5:15 ` Shravan.Chippa
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=20250305051442.3716817-4-shravan.chippa@microchip.com \
--to=shravan.chippa@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=praveen.kumar@microchip.com \
--cc=sakari.ailus@linux.intel.com \
--cc=valentina.fernandezalanis@microchip.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
all inboxes | Powered by JetHome®