From: Umang Jain <umang.jain@ideasonboard.com>
To: linux-media@vger.kernel.org
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Umang Jain <umang.jain@ideasonboard.com>
Subject: [PATCH 1/4] media: i2c: imx335: Drop setting of 0x3a00 register
Date: Thu, 25 Jan 2024 21:19:05 +0530 [thread overview]
Message-ID: <20240125154908.465191-2-umang.jain@ideasonboard.com> (raw)
In-Reply-To: <20240125154908.465191-1-umang.jain@ideasonboard.com>
Register 0x3a00 is a reserved field as per the IMX335 datasheet,
hence shouldn't be set by the driver.
Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
---
drivers/media/i2c/imx335.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/i2c/imx335.c b/drivers/media/i2c/imx335.c
index 5cca8d637952..0df9ea189fff 100644
--- a/drivers/media/i2c/imx335.c
+++ b/drivers/media/i2c/imx335.c
@@ -249,7 +249,6 @@ static const struct imx335_reg mode_2592x1940_regs[] = {
{0x3794, 0x7a},
{0x3796, 0xa1},
{0x37b0, 0x36},
- {0x3a00, 0x01},
};
static const struct imx335_reg raw10_framefmt_regs[] = {
--
2.41.0
next prev parent reply other threads:[~2024-01-25 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:49 [PATCH 0/4] imx335: Support additional link-freq and TPG Umang Jain
2024-01-25 15:49 ` Umang Jain [this message]
2024-01-25 16:05 ` [PATCH 1/4] media: i2c: imx335: Drop setting of 0x3a00 register Sakari Ailus
2024-01-25 15:49 ` [PATCH 2/4] media: i2c: imx335: Refactor power sequence to set controls Umang Jain
2024-01-25 15:49 ` [PATCH 3/4] media: i2c: imx335: Support multiple link frequency Umang Jain
2024-01-25 15:49 ` [PATCH 4/4] media: i2c: imx335: Add support for test pattern generator Umang Jain
2024-01-25 16:19 ` Sakari Ailus
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=20240125154908.465191-2-umang.jain@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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®