From: "Benoît Monin" <benoit.monin@bootlin.com>
To: linux-i2c@vger.kernel.org
Cc: "Jean Delvare" <jdelvare@suse.de>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Benoît Monin" <benoit.monin@bootlin.com>
Subject: [PATCH i2c-tools v2 1/2] i2cdetect: Display mangling and nostart support
Date: Tue, 23 Dec 2025 14:22:42 +0100 [thread overview]
Message-ID: <20251223-msg-flags-v2-1-8d934a4366e2@bootlin.com> (raw)
In-Reply-To: <20251223-msg-flags-v2-0-8d934a4366e2@bootlin.com>
Show the support of protocol mangling and repeated start elision in the
list of fonctionnalities displayed with '-F'.
Signed-off-by: Benoît Monin <benoit.monin@bootlin.com>
---
tools/i2cdetect.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/i2cdetect.c b/tools/i2cdetect.c
index bb2f146..70b585d 100644
--- a/tools/i2cdetect.c
+++ b/tools/i2cdetect.c
@@ -165,6 +165,10 @@ static const struct func all_func[] = {
{ .value = I2C_FUNC_SLAVE,
.name = "Target mode" },
#endif
+ { .value = I2C_FUNC_PROTOCOL_MANGLING,
+ .name = "Protocol mangling" },
+ { .value = I2C_FUNC_NOSTART,
+ .name = "Skip repeated start" },
{ .value = 0, .name = "" }
};
--
2.52.0
next prev parent reply other threads:[~2025-12-23 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 13:22 [PATCH i2c-tools v2 0/2] Add support for message modifier flags Benoît Monin
2025-12-23 13:22 ` Benoît Monin [this message]
2026-01-13 17:22 ` [PATCH i2c-tools v2 1/2] i2cdetect: Display mangling and nostart support Wolfram Sang
2025-12-23 13:22 ` [PATCH i2c-tools v2 2/2] i2ctransfer: Add optional message modifier flags Benoît Monin
2026-01-13 17:33 ` Wolfram Sang
2026-01-16 13:01 ` Benoît Monin
2026-01-20 15:06 ` Jean Delvare
2026-01-20 14:45 ` Jean Delvare
2026-01-13 17:21 ` [PATCH i2c-tools v2 0/2] Add support for " Wolfram Sang
2026-01-20 14:15 ` Jean Delvare
2026-01-21 10:00 ` Benoît Monin
2026-01-21 18:37 ` Jean Delvare
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=20251223-msg-flags-v2-1-8d934a4366e2@bootlin.com \
--to=benoit.monin@bootlin.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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