Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Tandra, Vasantha Likitha" <VasanthaLikitha.Tandra@amd.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"git (AMD-Xilinx)" <git@amd.com>,
	"jdelvare@suse.de" <jdelvare@suse.de>,
	"Datta, Shubhrajyoti" <shubhrajyoti.datta@amd.com>
Subject: Re: [PATCH] i2c-tools: i2ctransfer: Set I2C adapter timeout using I2C_TIMEOUT ioctl
Date: Tue, 21 Jul 2026 08:53:31 +0200	[thread overview]
Message-ID: <al8Xa6P7YYRwOn3D@shikoro> (raw)
In-Reply-To: <DM4PR12MB77657106776BE150FDCCF7C093C22@DM4PR12MB7765.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Hi,

>   Thanks for the review. Your suggestion makes sense to me - I'll move
>   it out of i2ctransfer and add -T (timeout) and -R (retries) to
>   i2cdetect instead. I agree a separate i2cconfig tool is not needed.

Great, thanks.

>   While checking the list of ioctls, I observed the I2C_TIMEOUT ioctl
>   to set the timeout, but I did not observe any "get" ioctl to read
>   the timeout value back from user space (same for retries). So
>   setting a value with -T/-R works, but reading the current value
>   (when no value is given) does not seem possible right now.

You are right. That shows how seldom those IOCTLs are used. I forgot
that one cannot read them, sorry about that.

>   Could you let me know how you would like me to handle this - should
>   I keep -T/-R as set-only for now?

Yes. This is the way to go.

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-07-21  6:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 16:34 [PATCH] i2c-tools: i2ctransfer: Set I2C adapter timeout using I2C_TIMEOUT ioctl Vasantha Likitha T
2026-07-20 22:10 ` Wolfram Sang
2026-07-21  5:17   ` Tandra, Vasantha Likitha
2026-07-21  6:53     ` Wolfram Sang [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=al8Xa6P7YYRwOn3D@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=VasanthaLikitha.Tandra@amd.com \
    --cc=git@amd.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=shubhrajyoti.datta@amd.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