public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Wenyuan Li <2063309626@qq.com>,
	Andy Walls <awalls@md.metrocast.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	gszhai@bjtu.edu.cn, 25125332@bjtu.edu.cn, 25125283@bjtu.edu.cn,
	23120469@bjtu.edu.cn, stable@vger.kernel.org
Subject: Re: [PATCH v4] media: tuner: check return value of I2C transfers in set_type()
Date: Tue, 5 May 2026 14:05:51 +0200	[thread overview]
Message-ID: <79449571-d8c6-4fa7-8d53-5b358b73d34f@kernel.org> (raw)
In-Reply-To: <tencent_46889E152DE22B7E8A0CBB3311C556F92E09@qq.com>

On 3/29/26 12:51, Wenyuan Li wrote:
> In set_type(), several I2C transfers are performed to initialize
> specific tuners (e.g. FMD1216ME, FMD1216MEX, TD1316), but the return
> value of i2c_master_send() is not checked.
> 
> If an I2C transfer fails, the initialization sequence may be
> incomplete, potentially leaving the tuner in an inconsistent state
> without any error being reported.
> 
> Check the return value of i2c_master_send() and propagate failures
> to the attach_failed path. A small helper is introduced to reduce
> duplication and provide consistent error reporting.
> 
> This ensures that I2C communication errors during tuner
> initialization are properly detected and handled.
> 
> Fixes: 93df3413f1b4 ("[PATCH] v4l: 655: added support for the philips td1316 tuner")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wenyuan Li <2063309626@qq.com>
> 
> ---
> v5:
> - Reword commit message to better explain rationale
> - Clarify error handling approach
> - No functional changes
> 
> v4:
> - Added Cc: stable@vger.kernel.org
> - Updated Fixes tag
> ---
>  drivers/media/v4l2-core/tuner-core.c | 22 +++++++++++++++++++---
>  1 file changed, 19 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/media/v4l2-core/tuner-core.c b/drivers/media/v4l2-core/tuner-core.c
> index 004ec4d7beea..01f28436a1f8 100644
> --- a/drivers/media/v4l2-core/tuner-core.c
> +++ b/drivers/media/v4l2-core/tuner-core.c
> @@ -280,6 +280,19 @@ static const struct analog_demod_ops tuner_analog_ops = {
>   * Functions to select between radio and TV and tuner probe/remove functions
>   */
>  
> +static int tuner_i2c_send(struct i2c_client *c, u8 *buf, int len)
> +{
> +	int ret = i2c_master_send(c, buf, len);
> +
> +	if (ret != len) {
> +		int err = ret < 0 ? ret : -EIO;
> +
> +		dev_err(&c->dev, "I2C send failed: %pe\n", ERR_PTR(err));
> +		return err;
> +	}
> +	return 0;
> +}
> +

I think this is overkill, and I also like to keep changes to this old code
to a minimum.

>  /**
>   * set_type - Sets the tuner type for a given device
>   *
> @@ -351,11 +364,13 @@ static void set_type(struct i2c_client *c, unsigned int type,
>  		buffer[1] = 0xdc;
>  		buffer[2] = 0x9c;
>  		buffer[3] = 0x60;
> -		i2c_master_send(c, buffer, 4);
> +		if (tuner_i2c_send(c, buffer, 4))
> +			goto attach_failed;

Just keep it simple:

		if (i2c_master_send(c, buffer, 4) != 4)
			goto attach_failed;

Ditto below.

>  		mdelay(1);
>  		buffer[2] = 0x86;
>  		buffer[3] = 0x54;
> -		i2c_master_send(c, buffer, 4);
> +		if (tuner_i2c_send(c, buffer, 4))
> +			goto attach_failed;
>  		if (!dvb_attach(simple_tuner_attach, &t->fe,
>  				t->i2c->adapter, t->i2c->addr, t->type))
>  			goto attach_failed;
> @@ -365,7 +380,8 @@ static void set_type(struct i2c_client *c, unsigned int type,
>  		buffer[1] = 0xdc;
>  		buffer[2] = 0x86;
>  		buffer[3] = 0xa4;
> -		i2c_master_send(c, buffer, 4);
> +		if (tuner_i2c_send(c, buffer, 4))
> +			goto attach_failed;
>  		if (!dvb_attach(simple_tuner_attach, &t->fe,
>  				t->i2c->adapter, t->i2c->addr, t->type))
>  			goto attach_failed;

Regards,

	Hans

      parent reply	other threads:[~2026-05-05 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 10:51 [PATCH v4] media: tuner: check return value of I2C transfers in set_type() Wenyuan Li
2026-03-29 12:00 ` Markus Elfring
2026-05-05 12:05 ` Hans Verkuil [this message]

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=79449571-d8c6-4fa7-8d53-5b358b73d34f@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=2063309626@qq.com \
    --cc=23120469@bjtu.edu.cn \
    --cc=25125283@bjtu.edu.cn \
    --cc=25125332@bjtu.edu.cn \
    --cc=awalls@md.metrocast.net \
    --cc=gszhai@bjtu.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stable@vger.kernel.org \
    /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