linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	kernel@pengutronix.de, andi.shyti@kernel.org,
	 shawnguo@kernel.org, s.hauer@pengutronix.de, Frank.Li@nxp.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,
	 Stefan Eichenberger <stefan.eichenberger@toradex.com>
Subject: Re: [PATCH v2 1/4] i2c: imx: only poll for bus busy in multi master mode
Date: Wed, 21 Aug 2024 13:43:49 -0300	[thread overview]
Message-ID: <CAOMZO5DW+Wz7AWPJCBXkdaMf3NRcZTAmj2Wo9rvwnH9pDGbSGg@mail.gmail.com> (raw)
In-Reply-To: <ZsYGbN36jwxyMAvE@eichest-laptop>

Hi Stefan and Oleksij,

On Wed, Aug 21, 2024 at 12:23 PM Stefan Eichenberger <eichest@gmail.com> wrote:

> Thanks a lot for testing. Are the other patches required as well or did
> only introducing the master mode flag solve the issue?

Only applying this one fixed the problem.

> > It looks like with this patch, the I2SR_IAL interrupt is not cleared.
> > I would expect some kind of interrupt storm. Can you confirm it?

I have just inspected 'cat /proc/interrupts' and no interrupt storm is seen.

Thanks

  reply	other threads:[~2024-08-21 16:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  7:19 [PATCH v2 0/4] i2c: imx: prevent rescheduling in non-dma mode Stefan Eichenberger
2024-08-19  7:19 ` [PATCH v2 1/4] i2c: imx: only poll for bus busy in multi master mode Stefan Eichenberger
2024-08-21 11:01   ` Fabio Estevam
2024-08-21 14:39     ` Oleksij Rempel
2024-08-21 15:23       ` Stefan Eichenberger
2024-08-21 16:43         ` Fabio Estevam [this message]
2024-08-21 22:31         ` Andi Shyti
2024-08-22  6:51     ` Oleksij Rempel
2024-08-22 11:07     ` Fabio Estevam
2024-08-22 11:50       ` Stefan Eichenberger
2024-08-22 12:59         ` Fabio Estevam
2024-08-23 13:43       ` Stefan Eichenberger
2024-08-21 22:21   ` Andi Shyti
2024-08-22  7:03     ` Stefan Eichenberger
2024-08-22 10:04       ` Oleksij Rempel
2024-08-22 12:03         ` Stefan Eichenberger
2024-08-23  0:35         ` Andi Shyti
2024-08-23 13:48           ` Stefan Eichenberger
2024-08-23 14:04             ` Oleksij Rempel
2024-08-23 14:42               ` Stefan Eichenberger
2024-08-19  7:19 ` [PATCH v2 2/4] i2c: imx: separate atomic, dma and non-dma use case Stefan Eichenberger
2024-08-30  7:31   ` Oleksij Rempel
2024-08-19  7:19 ` [PATCH v2 3/4] i2c: imx: use readb_relaxed and writeb_relaxed Stefan Eichenberger
2024-08-30  7:37   ` Oleksij Rempel
2024-08-19  7:19 ` [PATCH v2 4/4] i2c: imx: prevent rescheduling in non dma mode Stefan Eichenberger
2024-08-30  8:13   ` Oleksij Rempel

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=CAOMZO5DW+Wz7AWPJCBXkdaMf3NRcZTAmj2Wo9rvwnH9pDGbSGg@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=Frank.Li@nxp.com \
    --cc=andi.shyti@kernel.org \
    --cc=eichest@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stefan.eichenberger@toradex.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;
as well as URLs for NNTP newsgroup(s).