linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Oleksij Rempel <linux@rempel-privat.de>
Subject: Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
Date: Tue, 26 Apr 2016 23:35:27 +0200	[thread overview]
Message-ID: <20160426213527.GI4587@katana> (raw)
In-Reply-To: <1461652066-16456-1-git-send-email-dirk.behme@de.bosch.com>

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

On Tue, Apr 26, 2016 at 08:27:46AM +0200, Dirk Behme wrote:
> From: Oleksij Rempel <linux@rempel-privat.de>
> 
> Documentation/timers/timers-howto.txt recommends to use
> usleep_range on delays > 10usec. According to my test results
> with Neonode zForce touchscreen driver, usleep_range indeed
> reduces CPU load.
> 
> Stats collected with "./perf record -a -g -F 1000 sleep 10"
> 
> i2c-imx with udelay(50):
> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
>     ---irq_thread
>        |--33.75%--irq_thread_fn
>        |    |--19.27%--0x7f08a878
>        |    |     i2c_master_recv
>        |    |     i2c_transfer
>        |    |     __i2c_transfer
>        |    |     i2c_imx_xfer
>        |    |     |--11.71%--i2c_imx_trx_complete

Reworded $subject to match code and applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-04-26 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  6:27 [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50) Dirk Behme
2016-04-26 11:02 ` Vladimir Zapolskiy
2016-04-26 12:22   ` Dirk Behme
2016-04-26 21:35 ` Wolfram Sang [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=20160426213527.GI4587@katana \
    --to=wsa@the-dreams.de \
    --cc=dirk.behme@de.bosch.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    /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).