public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Monin" <benoit.monin@bootlin.com>
To: linux-i2c@vger.kernel.org
Cc: "Jean Delvare" <jdelvare@suse.de>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Benoît Monin" <benoit.monin@bootlin.com>
Subject: [PATCH i2c-tools v3 1/2] i2cdetect: Display mangling and nostart support
Date: Tue, 27 Jan 2026 10:25:57 +0100	[thread overview]
Message-ID: <20260127-msg-flags-v3-1-e7539945db2b@bootlin.com> (raw)
In-Reply-To: <20260127-msg-flags-v3-0-e7539945db2b@bootlin.com>

Show the support of protocol mangling and repeated start elision in
the list of fonctionnalities displayed with '-F'. We only use these
functionnalities if they are known at compile-time so i2cdetect can be
built against older kernels.

Signed-off-by: Benoît Monin <benoit.monin@bootlin.com>
---
 tools/i2cdetect.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/tools/i2cdetect.c b/tools/i2cdetect.c
index bb2f146..3c22f17 100644
--- a/tools/i2cdetect.c
+++ b/tools/i2cdetect.c
@@ -164,6 +164,14 @@ static const struct func all_func[] = {
 #if defined(I2C_FUNC_SLAVE)
 	{ .value = I2C_FUNC_SLAVE,
 	  .name = "Target mode" },
+#endif
+#if defined(I2C_FUNC_PROTOCOL_MANGLING)
+	{ .value = I2C_FUNC_PROTOCOL_MANGLING,
+	  .name = "Protocol mangling" },
+#endif
+#if defined(I2C_FUNC_NOSTART)
+	{ .value = I2C_FUNC_NOSTART,
+	  .name = "Repeated start skipping" },
 #endif
 	{ .value = 0, .name = "" }
 };

-- 
2.52.0


  reply	other threads:[~2026-01-27  9:26 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 ` Benoît Monin [this message]
2026-01-27  9:25 ` [PATCH i2c-tools v3 2/2] i2ctransfer: Add optional " Benoît Monin
2026-02-17 12:13 ` [PATCH i2c-tools v3 0/2] Add support for " Jean Delvare
2026-03-23  9:12   ` 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=20260127-msg-flags-v3-1-e7539945db2b@bootlin.com \
    --to=benoit.monin@bootlin.com \
    --cc=jdelvare@suse.de \
    --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