From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>
Cc: Vasantha Likitha T <vasanthalikitha.tandra@amd.com>,
Dmitry Guzman <Dmitry.Guzman@mobileye.com>,
Aniket Randive <quic_arandive@quicinc.com>,
linux-i2c@vger.kernel.org, jdelvare@suse.de, git@amd.com
Subject: Re: [PATCH] i2c-tools: i2ctransfer: Set I2C adapter timeout using I2C_TIMEOUT ioctl
Date: Wed, 22 Jul 2026 09:56:24 +0200 [thread overview]
Message-ID: <amB3qFSwbeDZ5l7Q@shikoro> (raw)
In-Reply-To: <67436ff9-e440-404a-a52f-e5b238256152@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
> Why userspace need to decide and set the timeout values for adapter ?
> Adapter knows the transfer frequency and transfer data length, it can be
> calculated by core layer itself and can set.
Freq and data length are not enough for timeout calculation. It is also
board specific (e.g. capacitance) and environment specific (surrounding
noise). It can be argued to modify it from userspace. Unclear how much
that is used in practice, though.
> Retrials can be fixed and hard coded for everyone.
I don't think we can remove the interface because of the "don't break
userspace" rule.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-22 7:56 UTC|newest]
Thread overview: 6+ 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
2026-07-22 6:06 ` Mukesh Savaliya
2026-07-22 7:56 ` 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=amB3qFSwbeDZ5l7Q@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Dmitry.Guzman@mobileye.com \
--cc=git@amd.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=quic_arandive@quicinc.com \
--cc=vasanthalikitha.tandra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.