From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Oleksandr Suvorov <oleksandr.suvorov@toradex.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] i2c: imx: Retry transfer on transient failure
Date: Tue, 12 Jul 2022 11:05:14 +0200 [thread overview]
Message-ID: <20220712090514.lt4r4dvlkn55jf2o@pengutronix.de> (raw)
In-Reply-To: <20220712082415.319738-1-francesco.dolcini@toradex.com>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Tue, Jul 12, 2022 at 10:24:15AM +0200, Francesco Dolcini wrote:
> From: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
>
> Set the i2c_adapter retries field to a sensible value. This allows
> the i2c core to retry master_xfer()/master_xfer_atomic() when it
> returns -EAGAIN. Currently the i2c-imx driver returns -EAGAIN only
> on Tx arbitration failure (I2SR_IAL).
>
> Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Additional to Marco's questions:
- I wouldn't have added a define for the constant as IMHO
i2c_imx->adapter.retries = 3;
is expressive enough. Thoughts?
- Is it right this is a driver specific setting? I would have expected
that this setting is in the realm of the i2c core. Grepping through
the drivers (git grep \\\<retries\\s\*= drivers/i2c/) shows a wide
variety between 0 and 5. (For some drivers you have do some deeper
checking than that grep because driver authors chose to use a define
for that; see above.)
- In which situations does this help? Please mention these in the
commit log.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-12 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 8:24 [PATCH v1] i2c: imx: Retry transfer on transient failure Francesco Dolcini
2022-07-12 8:47 ` Marco Felsch
2022-07-12 9:14 ` Francesco Dolcini
2022-07-12 11:32 ` Wolfram Sang
2022-07-12 12:02 ` Marco Felsch
2022-07-12 9:05 ` Uwe Kleine-König [this message]
2022-07-12 10:05 ` Francesco Dolcini
2022-07-13 11:57 ` Francesco Dolcini
2022-07-13 13:24 ` Oleksij Rempel
2022-07-13 13:43 ` Francesco Dolcini
2022-07-13 15:57 ` Oleksij Rempel
2022-07-13 20:25 ` Francesco Dolcini
2022-07-14 7:07 ` Oleksij Rempel
2022-07-14 7:34 ` Francesco Dolcini
2022-07-15 6:49 ` Uwe Kleine-König
2022-07-15 7:24 ` Francesco Dolcini
2022-07-15 8:34 ` Uwe Kleine-König
2022-07-15 11:45 ` Francesco Dolcini
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=20220712090514.lt4r4dvlkn55jf2o@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux@rempel-privat.de \
--cc=oleksandr.suvorov@toradex.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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