linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	spi-devel-general@lists.sourceforge.net,
	Lee Jones <lee.jones@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	Magnus Templing <magnus.templing@stericsson.com>
Subject: Re: [PATCH 1/2] spi/pl022: timeout on polled transfer v2
Date: Thu, 19 May 2011 20:06:32 +0200	[thread overview]
Message-ID: <BANLkTikR7A1Y4sumjZXS5ou3ex7PJOi1CA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=COt5Te4bF1M30A+R4Vqnz=kWiJA@mail.gmail.com>

2011/5/19 Vitaly Wool <vitalywool@gmail.com>:
> On Thu, May 19, 2011 at 7:36 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>>>
>>> just out of curiosity: is it a busy wait? Looks like it is...
>>
>> Yep that's the polling mode part. IRQ and DMA mode should
>> be the norm I guess.
>>
>> Magnus: do you have a specific use case for this thing?
>
> Well, adding cpu_relax() somewhere in the loop might be not a bad idea...

OK sent a patch for it, and Grant applied it within something like
30 seconds :-)

I think on ARM that just boils down to a barrier() so it
basically injects air in the pipeline when busywaiting, I never
understood what that is good for, but it's a good marker anyway.

Linus Walleij

      reply	other threads:[~2011-05-19 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 16:05 [PATCH 1/2] spi/pl022: timeout on polled transfer v2 Linus Walleij
2011-05-19 16:55 ` Grant Likely
     [not found] ` <1305821134-26147-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2011-05-19 17:04   ` Vitaly Wool
2011-05-19 17:36     ` Linus Walleij
2011-05-19 17:40       ` Vitaly Wool
2011-05-19 18:06         ` Linus Walleij [this message]

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=BANLkTikR7A1Y4sumjZXS5ou3ex7PJOi1CA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=magnus.templing@stericsson.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=vitalywool@gmail.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).