From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX27 SPI tx fifo underrun
Date: Thu, 14 Apr 2011 20:36:13 +0200 [thread overview]
Message-ID: <20110414183613.GH3811@pengutronix.de> (raw)
In-Reply-To: <io73tm$1e5$1@dough.gmane.org>
On Thu, Apr 14, 2011 at 05:29:57PM +0200, Jurgen Braam wrote:
> while trying to write to an at25 eeprom connected via SPI on an
> i.MX27, I ran into a TX FIFO underrun. In spi_imx_isr() the variable
> spi_imx->txfifo gets rather large as a result of an unsigned integer
> underflow, resulting in a feels-like-endless loop.
>
> The following patch fixes the problem in our case:
>
> --- a/drivers/spi/spi_imx.c
> +++ b/drivers/spi/spi_imx.c
> @@ -407,7 +407,7 @@ static void __maybe_unused
Please add your Signed-off-by: when sending patches.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-04-14 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 15:29 i.MX27 SPI tx fifo underrun Jurgen Braam
2011-04-14 18:36 ` Robert Schwebel [this message]
2011-04-14 18:43 ` Wolfram Sang
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=20110414183613.GH3811@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).