[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251201000026.690298-1-xiaolei.wang@windriver.com>
Date: Mon, 1 Dec 2025 08:00:26 +0800
From: Xiaolei Wang <xiaolei.wang@...driver.com>
To: sakari.ailus@...ux.intel.com, dave.stevenson@...pberrypi.com,
jacopo@...ndi.org, mchehab@...nel.org,
prabhakar.mahadev-lad.rj@...renesas.com,
laurent.pinchart@...asonboard.com, hverkuil+cisco@...nel.org,
Xiaolei.Wang@...driver.com
Cc: linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] media: i2c: ov5647: use our own mutex for the ctrl lock
__v4l2_ctrl_handler_setup() and __v4l2_ctrl_modify_range()
contains an assertion to verify that the v4l2_ctrl_handler::lock
is held, as it should only be called when the lock has already
been acquired. Therefore use our own mutex for the ctrl lock,
otherwise a warning will be reported.
Signed-off-by: Xiaolei Wang <xiaolei.wang@...driver.com>
---
drivers/media/i2c/ov5647.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/i2c/ov5647.c b/drivers/media/i2c/ov5647.c
index e193fef4fced..4e14eefba577 100644
--- a/drivers/media/i2c/ov5647.c
+++ b/drivers/media/i2c/ov5647.c
@@ -1288,9 +1288,12 @@ static int ov5647_init_controls(struct ov5647 *sensor)
{
struct i2c_client *client = v4l2_get_subdevdata(&sensor->sd);
int hblank, exposure_max, exposure_def;
+ struct v4l2_ctrl_handler *hdl = &sensor->ctrls;
v4l2_ctrl_handler_init(&sensor->ctrls, 9);
+ hdl->lock = &sensor->lock;
+
v4l2_ctrl_new_std(&sensor->ctrls, &ov5647_ctrl_ops,
V4L2_CID_AUTOGAIN, 0, 1, 1, 0);
--
2.43.0
Powered by blists - more mailing lists