From: Michael Riesch <michael.riesch@collabora.com>
To: Narasimharao Vadlamudi <ahmisaranrao@gmail.com>,
sakari.ailus@linux.intel.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: imx415: Fix control error handling
Date: Mon, 3 Aug 2026 15:14:57 +0200 [thread overview]
Message-ID: <3c62ce01-e052-490b-a61d-b134a3b3b8fe@collabora.com> (raw)
In-Reply-To: <20260731125542.293895-1-ahmisaranrao@gmail.com>
Hi Narasimharao Vadlamudi,
Thanks for the patch!
On 7/31/26 14:55, Narasimharao Vadlamudi wrote:
> imx415_set_testpattern() accumulates failures from cci_write(), but drops
> the value and always returns success. Return the accumulated error so V4L2
> reports failures to userspace.
>
> The VBLANK path also returned immediately when programming VMAX failed
> after pm_runtime_get_if_in_use() had taken a runtime PM reference. Break
> out of the switch instead so the common pm_runtime_put() path is used.
>
> Fixes: d5df1c7f3f83 ("media: i2c: imx415: Convert to new CCI register access helpers")
> Fixes: 3bcae55ab96a ("media: i2c: imx415: Add read/write control of VBLANK")
> Signed-off-by: Narasimharao Vadlamudi <ahmisaranrao@gmail.com>
Reviewed-by: Michael Riesch <michael.riesch@collabora.com>
Best regards,
Michael
> ---
> drivers/media/i2c/imx415.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/i2c/imx415.c b/drivers/media/i2c/imx415.c
> index 0b424c17e880..c3b22b238ea0 100644
> --- a/drivers/media/i2c/imx415.c
> +++ b/drivers/media/i2c/imx415.c
> @@ -686,7 +686,7 @@ static int imx415_set_testpattern(struct imx415 *sensor, int val)
> cci_write(sensor->regmap, IMX415_DIG_CLP_MODE, 0x01, &ret);
> cci_write(sensor->regmap, IMX415_WRJ_OPEN, 0x01, &ret);
> }
> - return 0;
> + return ret;
> }
>
> static int imx415_s_ctrl(struct v4l2_ctrl *ctrl)
> @@ -720,7 +720,7 @@ static int imx415_s_ctrl(struct v4l2_ctrl *ctrl)
> ret = cci_write(sensor->regmap, IMX415_VMAX,
> format->height + ctrl->val, NULL);
> if (ret)
> - return ret;
> + break;
> /*
> * Exposure is set based on VMAX which has just changed, so
> * program exposure register as well
next prev parent reply other threads:[~2026-08-03 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 12:55 [PATCH] media: i2c: imx415: Fix control error handling Narasimharao Vadlamudi
2026-08-03 13:14 ` Michael Riesch [this message]
2026-08-03 13:22 ` Jacopo Mondi
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=3c62ce01-e052-490b-a61d-b134a3b3b8fe@collabora.com \
--to=michael.riesch@collabora.com \
--cc=ahmisaranrao@gmail.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;
as well as URLs for NNTP newsgroup(s).