Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Salah Triki <salah.triki@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Stepan Ionichev" <sozdayvek@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] iio: humidity: ens210: Extend I2C functionality check
Date: Sun, 23 Aug 2026 01:34:07 +0100	[thread overview]
Message-ID: <20260823013407.434a2247@jic23-huawei> (raw)
In-Reply-To: <20260819103110.25718-1-salah.triki@gmail.com>

On Wed, 19 Aug 2026 11:31:09 +0100
Salah Triki <salah.triki@gmail.com> wrote:

> The ENS210 driver uses byte data read/write, word data read, and block
> data read transactions. However, the probe function checks for
> I2C_FUNC_SMBUS_WRITE_BYTE (which is unused) and misses the check for word
> data reads.
> 
> Update the functionality check to strictly match the transactions used by
> the driver by removing the unused flag and adding the missing byte and word
> read capabilities.
> 
> Signed-off-by: Salah Triki <salah.triki@gmail.com>
I am a bit curious about whether any modern smbus capable controllers actually
support only a subset and without that info I don't want to see lots
of patches adding these checks

In this case there was a wrong check though so I'm very happy to see
that tidied!

Applied to the testing branch of iio.git

Thanks

Jonathan

> ---
> Changes since v7:
> - Fixed functionality mask based on code analysis by Stepan Ionichev and
>   Jonathan Cameron:
>   - Removed unused I2C_FUNC_SMBUS_WRITE_BYTE.
>   - Replaced I2C_FUNC_SMBUS_WRITE_BYTE_DATA with I2C_FUNC_SMBUS_BYTE_DATA.
>   - Used I2C_FUNC_SMBUS_READ_WORD_DATA
> 
> Changes since v6:
> - Replaced the incorrect use of I2C_FUNC_SMBUS_EMUL with an explicit
>   list of required SMBus functionalities as requested by Jonathan Cameron.
> - Used combined macros (BYTE_DATA, WORD_DATA) to simplify the check.
> 
> Changes since v5:
> - Changed patch title from "Fix missing I2C functionality checks" to
>   "Simplify I2C functionality check" to reflect the new approach.
> - Dropped the Fixes tag as the change is now considered hardening rather
>   than a bug fix.
> - Replaced individual functionality checks with a single check for
>   I2C_FUNC_SMBUS_EMUL as suggested by Jonathan Cameron.
> 
> Changes since v4:
> - Fixed the alignment and indentation of the I2C functionality check
>   per Andy's review.
> 
> Changes since v3:
> - Fixed the alignment and indentation of the I2C functionality check
>   per Andy's review.
> 
> Changes since v2:
> - Fixed the alignment and indentation of the I2C functionality check
>   per Maxime's review.
> 
> Changes since v1:
> - Updated the I2C functionality test to check for both required native
>   operations and SMBus emulation (`I2C_FUNC_SMBUS_EMUL`)
> 
>  drivers/iio/humidity/ens210.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/humidity/ens210.c b/drivers/iio/humidity/ens210.c
> index 81276195152b..4bdd37e7227b 100644
> --- a/drivers/iio/humidity/ens210.c
> +++ b/drivers/iio/humidity/ens210.c
> @@ -202,8 +202,8 @@ static int ens210_probe(struct i2c_client *client)
>  	int ret;
>  
>  	if (!i2c_check_functionality(client->adapter,
> -				     I2C_FUNC_SMBUS_WRITE_BYTE_DATA |
> -				     I2C_FUNC_SMBUS_WRITE_BYTE |
> +				     I2C_FUNC_SMBUS_BYTE_DATA |
> +				     I2C_FUNC_SMBUS_READ_WORD_DATA |
>  				     I2C_FUNC_SMBUS_READ_I2C_BLOCK)) {
>  		return dev_err_probe(&client->dev, -EOPNOTSUPP,
>  			"adapter does not support some i2c transactions\n");


      reply	other threads:[~2026-08-23  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 10:31 [PATCH v8] iio: humidity: ens210: Extend I2C functionality check Salah Triki
2026-08-23  0:34 ` Jonathan Cameron [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=20260823013407.434a2247@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=salah.triki@gmail.com \
    --cc=sozdayvek@gmail.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