From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Lucas Tanure <tanureal@opensource.cirrus.com>
Cc: Mark Brown <broonie@kernel.org>, <patches@opensource.cirrus.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regmap: debugfs: Jump to the next readable register
Date: Tue, 19 Mar 2019 11:14:12 +0000 [thread overview]
Message-ID: <20190319111412.GQ46536@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20190319094133.8843-2-tanureal@opensource.cirrus.com>
On Tue, Mar 19, 2019 at 09:41:33AM +0000, Lucas Tanure wrote:
> Improve the speed of the loop jumping to the next
> available register
>
> Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
> ---
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
A very brief look shows a pretty reasonable speed up on the
massive wm5110 register map.
First regmap cat on wm5110:
pre-patch:
real 2m40.865s
sys 2m21.104s
post-patch:
real 2m16.550s
sys 2m5.799s
Repeat cat on wm5110:
pre-patch:
real 2m5.635s
sys 2m0.030s
post-patch:
real 1m45.539s
sys 1m44.552s
Thanks,
Charles
prev parent reply other threads:[~2019-03-19 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 9:41 [PATCH 1/2] regmap: debugfs: Replace code by already existing function Lucas Tanure
2019-03-19 9:41 ` [PATCH 2/2] regmap: debugfs: Jump to the next readable register Lucas Tanure
2019-03-19 11:14 ` Charles Keepax [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=20190319111412.GQ46536@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=tanureal@opensource.cirrus.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
all inboxes | Powered by JetHome®