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 0/4] media: i2c: imx334: Add support for 1280x720 & 640x480 resolutions
Date: Wed, 5 Mar 2025 10:44:38 +0530 [thread overview]
Message-ID: <20250305051442.3716817-1-shravan.chippa@microchip.com> (raw)
From: Shravan Chippa <shravan.chippa@microchip.com>
Changelog:
v6 -> v7:
Add new patch: common reg value correction
v5 -> v6:
split the patches from two to three
1) Optimized the resolution arrays by integrating a common register array
2) 3840x2160 mode restored with reset values of imx334
3) 1280x720@30 and 640x480@30 resolutions
v4 -> v5:
Divided the patch into two separate patches:
- One for common register array values with existing resolutions
- Another for new modes supporting 640x480 and 1280x720 resolutions
v3 -> v4:
In response to the review request, the dependency of the common register
value array on the 445M link frequency has been eliminated.
Although I do not have a test setup for 4k resolution at an 819M
link frequency, I have made adjustments based on the IMX334 data sheet,
the latest 4k resolution, and the common register value array.
Additionally, the 4k resolution has been switched to master mode to
ensure consistency with other resolutions that also use master mode.
v2 -> v3:
removied blank lines reported by media CI robot
v1 -> v2:
Optimized the resolution arrays by added common register
array
---
Shravan Chippa (4):
media: i2c: imx334: Optimized 4k and 2k mode register arrays
media: i2c: imx334: common reg value correction
media: i2c: imx334: update mode_3840x2160_regs array
media: i2c: imx334: add modes for 720p and 480p resolutions
drivers/media/i2c/imx334.c | 205 +++++++++++++++++++------------------
1 file changed, 103 insertions(+), 102 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-05 5:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 5:14 shravan kumar [this message]
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 ` [PATCH V7 3/4] media: i2c: imx334: update mode_3840x2160_regs array shravan kumar
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-1-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®