public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: "Benoît Monin" <benoit.monin@bootlin.com>
Cc: linux-i2c@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH i2c-tools v3 0/2] Add support for message modifier flags
Date: Tue, 17 Feb 2026 13:13:48 +0100	[thread overview]
Message-ID: <20260217131348.007dde93@endymion> (raw)
In-Reply-To: <20260127-msg-flags-v3-0-e7539945db2b@bootlin.com>

Hi Benoît,

On Tue, 27 Jan 2026 10:25:56 +0100, Benoît Monin wrote:
> I2C messages can be modified with a set of flags covered by the protocol
> mangling and the skip repeated start functionalities. This series add
> support for such flags to i2cdetect and i2ctransfer.
> 
> The first patch shows the support of protocol mangling and repeated
> start skipping in the output of 'i2cdetect -F'.
> 
> The second patch adds the parsing of optional flags to i2ctransfer
> message description. Those command-line flags then set the i2c message
> flags alongside the read/write flag.
> 
> I wrote these changes to test the insertion of I2C_M_STOP flag in
> multi-message transactions with i2ctransfer, but the other flags may be
> useful for various test scenarios. 
> 
> Signed-off-by: Benoît Monin <benoit.monin@bootlin.com>
> ---
> Changes in v3:
> - Use ifdefs to check that the flags and functionalities are known
>   at compile-time.
> - Check that the adapter supports the requested flags before using them
>   in i2ctransfer.
> - Add a warning in i2ctransfer man page about the risk of using these
>   flags.
> - Link to v2: https://lore.kernel.org/r/20251223-msg-flags-v2-0-8d934a4366e2@bootlin.com
> 
> Changes in v2:
> - Document the flags in i2ctransfer.8 man page.
> - Link to v1: https://lore.kernel.org/r/20251128-msg-flags-v1-0-6353f26fa6bc@bootlin.com
> 
> ---
> Benoît Monin (2):
>       i2cdetect: Display mangling and nostart support
>       i2ctransfer: Add optional message modifier flags
> 
>  tools/i2cdetect.c   |   8 ++++
>  tools/i2ctransfer.8 |  28 ++++++++++++-
>  tools/i2ctransfer.c | 119 ++++++++++++++++++++++++++++++++++++++++++++++------
>  3 files changed, 141 insertions(+), 14 deletions(-)

Both patches look very good to me. I was able to test the i2cdetect
patch and did not find any issue. I can't easily test the i2ctransfer
patch though.

Wolfram, can you please give some basic testing to the i2ctransfer
patch? Not necessarily with the mangling flags, but at least test that
the changes do not introduce any regression for your own use cases?

Thanks,
-- 
Jean Delvare
SUSE L3 Support

  parent reply	other threads:[~2026-02-17 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  9:25 [PATCH i2c-tools v3 0/2] Add support for message modifier flags Benoît Monin
2026-01-27  9:25 ` [PATCH i2c-tools v3 1/2] i2cdetect: Display mangling and nostart support Benoît Monin
2026-01-27  9:25 ` [PATCH i2c-tools v3 2/2] i2ctransfer: Add optional message modifier flags Benoît Monin
2026-02-17 12:13 ` Jean Delvare [this message]
2026-03-23  9:12   ` [PATCH i2c-tools v3 0/2] Add support for " Benoît Monin

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=20260217131348.007dde93@endymion \
    --to=jdelvare@suse.de \
    --cc=benoit.monin@bootlin.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wsa+renesas@sang-engineering.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