Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Romain Gantois" <romain.gantois@bootlin.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] iio: temperature: tmp117: add TI TMP119 support
Date: Mon, 08 Jun 2026 16:04:06 +0000	[thread overview]
Message-ID: <20260608160407.465C01F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260608-tmp119-v2-2-30c3537d5097@bootlin.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] TMP119 devices are incorrectly assigned `tmp117_channels_info` during hardware probe, resulting in the wrong IIO device name.
--

commit 39dc1c3727920cc7af5409c8327a8bd65880f8b8
Author: Wil Stark <wil_stark@keysight.com>

iio: temperature: tmp117: add TI TMP119 support

This commit adds support for the TMP119 temperature sensor. It introduces
the device ID, channel info, and matching data to allow the tmp117 driver
to handle TMP119 devices.

> diff --git a/drivers/iio/temperature/tmp117.c b/drivers/iio/temperature/tmp117.c
> index 8972083d903a2..18ad40f3e7361 100644
> --- a/drivers/iio/temperature/tmp117.c
> +++ b/drivers/iio/temperature/tmp117.c

[ ... ]

> @@ -170,6 +177,7 @@ static int tmp117_probe(struct i2c_client *client)
>  		match_data = &tmp116_channels_info;
>  		break;
>  	case TMP117_DEVICE_ID:
> +	case TMP119_DEVICE_ID:
>  		match_data = &tmp117_channels_info;
>  		break;

[Severity: Medium]
Will this assignment cause TMP119 devices to be registered with the wrong name?

By falling through to the TMP117_DEVICE_ID case, match_data is assigned to
&tmp117_channels_info rather than the newly added tmp119_channels_info.

As a result, TMP119 devices are exposed to userspace in the IIO subsystem
with the name 'tmp117' instead of 'tmp119'. The new tmp119_channels_info
struct appears to be completely bypassed during the hardware probe unless
identification fails and fallback match data is used.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260608-tmp119-v2-0-30c3537d5097@bootlin.com?part=2

  reply	other threads:[~2026-06-08 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 16:00 [PATCH v2 0/2] iio: temperature: tmp117: Support the TMP119 sensor Romain Gantois
2026-06-08 16:00 ` [PATCH v2 1/2] dt-bindings: iio: ti,tmp117: add binding for the TMP119 Romain Gantois
2026-06-08 17:12   ` Conor Dooley
2026-06-08 17:13     ` Conor Dooley
2026-06-08 17:22   ` Rob Herring (Arm)
2026-06-08 16:00 ` [PATCH v2 2/2] iio: temperature: tmp117: add TI TMP119 support Romain Gantois
2026-06-08 16:04   ` sashiko-bot [this message]
2026-06-08 17:24 ` [PATCH v2 0/2] iio: temperature: tmp117: Support the TMP119 sensor Jonathan Cameron

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=20260608160407.465C01F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=romain.gantois@bootlin.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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