public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Fend <matthias.fend@emfend.at>
To: Jimmy Su <jimmy.su@intel.com>,
	 Sakari Ailus <sakari.ailus@linux.intel.com>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org,
	Matthias Fend <matthias.fend@emfend.at>,
	 bsp-development.geo@leica-geosystems.com
Subject: [PATCH v2 3/9] media: i2c: ov08d10: remove duplicate register write
Date: Mon, 09 Mar 2026 18:07:05 +0100	[thread overview]
Message-ID: <20260309-ov08d10-v2-3-81f8b5d99984@emfend.at> (raw)
In-Reply-To: <20260309-ov08d10-v2-0-81f8b5d99984@emfend.at>

Register P1:0x33 is written twice with the same value in the
'lane_2_mode_1632x1224' sequence. Remove one unnecessary write access.

Signed-off-by: Matthias Fend <matthias.fend@emfend.at>
---
 drivers/media/i2c/ov08d10.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/media/i2c/ov08d10.c b/drivers/media/i2c/ov08d10.c
index 5e1b8b58b3d64bcf20a7b1a4e47f547d2fd82998..9d54170cdf7da6fe4f03dbf64d5e8976df247846 100644
--- a/drivers/media/i2c/ov08d10.c
+++ b/drivers/media/i2c/ov08d10.c
@@ -381,7 +381,6 @@ static const struct ov08d10_reg lane_2_mode_1632x1224[] = {
 	{0x07, 0x05},
 	{0x21, 0x02},
 	{0x24, 0x30},
-	{0x33, 0x03},
 	{0x31, 0x06},
 	{0x33, 0x03},
 	{0x01, 0x03},

-- 
2.34.1


  parent reply	other threads:[~2026-03-09 17:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 17:07 [PATCH v2 0/9] drivers: media: i2c: Omnivision OV08D10 improvements Matthias Fend
2026-03-09 17:07 ` [PATCH v2 1/9] media: i2c: ov08d10: fix runtime PM handling in probe Matthias Fend
2026-03-10  9:12   ` Philipp Zabel
2026-03-09 17:07 ` [PATCH v2 2/9] media: i2c: ov08d10: fix image vertical start setting Matthias Fend
2026-03-09 17:07 ` Matthias Fend [this message]
2026-03-09 17:07 ` [PATCH v2 4/9] media: i2c: ov08d10: fix some typos in comments Matthias Fend
2026-03-09 17:07 ` [PATCH v2 5/9] media: i2c: ov08d10: add missing newline to prints Matthias Fend
2026-03-09 17:07 ` [PATCH v2 6/9] dt-bindings: media: i2c: document Omnivision OV08D10 CMOS image sensor Matthias Fend
2026-03-10  8:27   ` Krzysztof Kozlowski
2026-03-17  8:44   ` Sakari Ailus
2026-03-09 17:07 ` [PATCH v2 7/9] media: i2c: ov08d10: add support for binding via device tree Matthias Fend
2026-03-09 17:07 ` [PATCH v2 8/9] media: i2c: ov08d10: add support for reset and power management Matthias Fend
2026-03-17  8:46   ` Sakari Ailus
2026-03-24  8:12     ` Matthias Fend
2026-03-24 10:32       ` Sakari Ailus
2026-03-09 17:07 ` [PATCH v2 9/9] media: i2c: ov08d10: add support for 24 MHz input clock Matthias Fend

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=20260309-ov08d10-v2-3-81f8b5d99984@emfend.at \
    --to=matthias.fend@emfend.at \
    --cc=bsp-development.geo@leica-geosystems.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jimmy.su@intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@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