From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lubomir Rintel <lkundrak@v3.sk>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in next with spi return from transfer_one()
Date: Thu, 15 Nov 2018 16:07:09 -0800 [thread overview]
Message-ID: <20181116000709.GK53235@atomide.com> (raw)
In-Reply-To: <20181116000154.GS2089@sirena.org.uk>
* Mark Brown <broonie@kernel.org> [181116 00:02]:
> On Thu, Nov 15, 2018 at 03:44:00PM -0800, Tony Lindgren wrote:
>
> > It seems to be caused because of the now missing "if (ret > 0) {"
> > line somehow that was there earlier. New code sets ms to 200 it
> > seems, then dmesg shows:
>
> Doh, of course :( Sorry I missed that.
>
> > The old code is not updating ms and it's set to 1.
>
> Right, and not waiting either which should be the issue. Does the
> following work:
And it's recalculating the timeout every time now too :) Yup that
fix works and the problem makes sense now:
Tested-by: Tony Lindgren <tony@atomide.com>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 498d3b9bf3ae..430ad637c643 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1114,9 +1114,11 @@ static int spi_transfer_one_message(struct spi_controller *ctlr,
> goto out;
> }
>
> - ret = spi_transfer_wait(ctlr, msg, xfer);
> - if (ret < 0)
> - msg->status = ret;
> + if (ret > 0) {
> + ret = spi_transfer_wait(ctlr, msg, xfer);
> + if (ret < 0)
> + msg->status = ret;
> + }
> } else {
> if (xfer->len)
> dev_err(&msg->spi->dev,
next prev parent reply other threads:[~2018-11-16 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 21:14 Regression in next with spi return from transfer_one() Tony Lindgren
2018-11-15 22:12 ` Mark Brown
2018-11-15 23:44 ` Tony Lindgren
2018-11-16 0:01 ` Mark Brown
2018-11-16 0:07 ` Tony Lindgren [this message]
2018-11-16 15:35 ` Lubomir Rintel
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=20181116000709.GK53235@atomide.com \
--to=tony@atomide.com \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=pavel@ucw.cz \
/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