From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c-s3c2410: Remove unconditional 1ms delay on each transfer
Date: Fri, 2 Apr 2010 14:13:46 +0100 [thread overview]
Message-ID: <20100402131346.GA28023@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <p2q1b68c6791004020600g283db571gacd0f8b7e4ddaf6@mail.gmail.com>
On Fri, Apr 02, 2010 at 10:00:52PM +0900, jassi brar wrote:
> On Fri, Apr 2, 2010 at 9:39 PM, Mark Brown
> > + ? ? ? /* first, try busy waiting briefly */
> > + ? ? ? spins = 0;
> ^^^^^^^^^^^^ ?
Gnargh, this is bit rot from my initial version which didn't have the
fallback for the multi-master case (I don't actually have any hardware
that can trigger that). As you can see from the fact that I was able to
test this successfully most transfers report idle on the first check
anyway.
Thanks.
prev parent reply other threads:[~2010-04-02 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 12:39 [PATCH] i2c-s3c2410: Remove unconditional 1ms delay on each transfer Mark Brown
2010-04-02 13:00 ` jassi brar
2010-04-02 13:13 ` Mark Brown [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=20100402131346.GA28023@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--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).