From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: o.rempel@pengutronix.de, kernel@pengutronix.de,
andi.shyti@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com, jic23@kernel.org,
lars@metafoo.de, nuno.sa@analog.com,
u.kleine-koenig@pengutronix.de, marcelo.schmitt@analog.com,
gnstark@salutedevices.com, francesco.dolcini@toradex.com,
linux-i2c@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Stefan Eichenberger <stefan.eichenberger@toradex.com>
Subject: Re: [RFC PATCH] i2c: imx: avoid rescheduling when waiting for bus not busy
Date: Fri, 31 May 2024 17:45:10 +0300 [thread overview]
Message-ID: <Zlnidi62gEWwdQ3U@smile.fi.intel.com> (raw)
In-Reply-To: <20240531142437.74831-1-eichest@gmail.com>
On Fri, May 31, 2024 at 04:24:37PM +0200, Stefan Eichenberger wrote:
> From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
>
> On our i.MX8M Mini based module we have an ADS1015 I2C ADC connected to
> the I2C bus. The ADS1015 I2C ADC will timeout after 25ms when the I2C
> bus is idle. The imx i2c driver will call schedule when waiting for the
> bus to become idle after switching to master mode. When the i2c
> controller switches to master mode it pulls SCL and SDA low, if the
> ADS1015 I2C ADC sees this for more than 25 ms without seeing SCL
> clocking, it will timeout and ignore all signals until the next start
> condition occurs (SCL and SDA low). This can occur when the system load
> is high and schedule returns after more than 25 ms.
>
> This rfc tries to solve the problem by using a udelay for the first 10
> ms before calling schedule. This reduces the chance that we will
> reschedule. However, it is still theoretically possible for the problem
> to occur. To properly solve the problem, we would also need to disable
> interrupts during the transfer.
>
> After some internal discussion, we see three possible solutions:
> 1. Use udelay as shown in this rfc and also disable the interrupts
> during the transfer. This would solve the problem but disable the
> interrupts. Also, we would have to re-enable the interrupts if the
> timeout is longer than 1ms (TBD).
> 2. We use a retry mechanism in the ti-ads1015 driver. When we see a
> timeout, we try again.
> 3. We use the suggested solution and accept that there is an edge case
> where the timeout can happen.
>
> There may be a better way to do this, which is why this is an RFC.
...
> + /*
> + * Avoid rescheduling in the first 10 ms to avoid
> + * timeouts for SMBus like devices
> + */
> + if (time_before(jiffies, orig_jiffies + msecs_to_jiffies(10)))
> + udelay(10);
> + else
> + schedule();
Isn't there cond_resched() or so for such things?
More info here: 494e46d08d35 ("airo: Replace in_atomic() usage.")
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-31 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 14:24 [RFC PATCH] i2c: imx: avoid rescheduling when waiting for bus not busy Stefan Eichenberger
2024-05-31 14:45 ` Andy Shevchenko [this message]
2024-06-03 7:43 ` Stefan Eichenberger
2024-06-02 14:31 ` Andrew Lunn
2024-06-03 7:34 ` Stefan Eichenberger
2024-06-21 15:22 ` Stefan Eichenberger
2024-06-21 17:24 ` Francesco Dolcini
2024-06-22 5:02 ` Oleksij Rempel
2024-06-24 15:49 ` Stefan Eichenberger
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=Zlnidi62gEWwdQ3U@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=eichest@gmail.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=gnstark@salutedevices.com \
--cc=imx@lists.linux.dev \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.eichenberger@toradex.com \
--cc=u.kleine-koenig@pengutronix.de \
/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