linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Alexander Stein
	<alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>
Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
	Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	Feng Tang <feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] i2c-eg20t: Rework pch_i2c_wait_for_bus_idle to reduce wait time
Date: Fri, 24 Feb 2012 13:17:53 +0100	[thread overview]
Message-ID: <20120224121753.GE2479@pengutronix.de> (raw)
In-Reply-To: <1329725656-32715-1-git-send-email-alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

On Mon, Feb 20, 2012 at 09:14:16AM +0100, Alexander Stein wrote:
> If you insert several i2c transfers, the driver might start the next one
> while the STOP bit of the previous transfer is still on the bus, marking
> the bus as busy.
> pch_i2c_wait_for_bus_idle does an msleep(20) delaying the next transfer
> by >=20ms. Reduce wait time by actively waiting 5 us once, then using
> usleep_range.
> 
> Signed-off-by: Alexander Stein <alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>

Tomoya, are you happy with it? (I hope he reads the list, since his
companies mailserver doesn't seem to accept my mails).

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-02-24 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  8:14 [PATCH v2] i2c-eg20t: Rework pch_i2c_wait_for_bus_idle to reduce wait time Alexander Stein
     [not found] ` <1329725656-32715-1-git-send-email-alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org>
2012-02-24 12:17   ` Wolfram Sang [this message]
     [not found]     ` <20120224121753.GE2479-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-02-27 23:53       ` Tomoya MORINAGA
     [not found]         ` <CANKRQngWB8kUO68UdbDeWey5eGRF0nGCE341j8jyCMogvYUYKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-01 10:15           ` Wolfram Sang
     [not found]             ` <20120301101502.GB2535-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-03-02  0:51               ` Tomoya MORINAGA
     [not found]                 ` <CANKRQniA2icHddFG22r7VtLTuoefbK61tpcUQnXgShFHuffUuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-06  7:36                   ` Alexander Stein
2012-03-07 18:16                     ` 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=20120224121753.GE2479@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=alexander.stein-93q1YBGzJSMe9JSWTWOYM3xStJ4P+DSV@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).