From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH i2c-tools] i2cdetect: display more functionality bits with '-F'
Date: Tue, 29 Nov 2022 12:31:28 +0100 [thread overview]
Message-ID: <20221129123128.06cf7b1d@endymion.delvare> (raw)
In-Reply-To: <20221119215646.6818-1-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Sat, 19 Nov 2022 22:56:46 +0100, Wolfram Sang wrote:
> Original motivation was to add I2C_FUNC_SLAVE, so users can easily
> find out if their hardware supports being a target. While here, add
> HostNotify and 10-bit addressing as well.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Fine with me, with one request below.
> ---
>
> Now, we could also add PROTOCOL_MANGLING and NO_START to have them all.
> But I am not sure if they are really helpful for users?
>
> tools/i2cdetect.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/i2cdetect.c b/tools/i2cdetect.c
> index 066ec82..54b78e2 100644
> --- a/tools/i2cdetect.c
> +++ b/tools/i2cdetect.c
> @@ -160,6 +160,12 @@ static const struct func all_func[] = {
> .name = "I2C Block Write" },
> { .value = I2C_FUNC_SMBUS_READ_I2C_BLOCK,
> .name = "I2C Block Read" },
> + { .value = I2C_FUNC_SMBUS_HOST_NOTIFY,
> + .name = "SMBus HostNotify" },
I'm not a big fan of gluing words. "SMBus Host Notify" please.
> + { .value = I2C_FUNC_10BIT_ADDR,
> + .name = "10-bit addressing" },
> + { .value = I2C_FUNC_SLAVE,
> + .name = "Target mode" },
> { .value = 0, .name = "" }
> };
>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2022-11-29 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 21:56 [PATCH i2c-tools] i2cdetect: display more functionality bits with '-F' Wolfram Sang
2022-11-29 11:31 ` Jean Delvare [this message]
2022-12-05 10:12 ` Wolfram Sang
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=20221129123128.06cf7b1d@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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