All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudheer" <spapothi@codeaurora.org>
To: 'Mark Brown' <broonie@kernel.org>
Cc: plai@codeaurora.org, bgoswami@codeaurora.org,
	alsa-devel@alsa-project.org
Subject: Using regmap_multi_reg_write() with regcache_sync()
Date: Thu, 30 Jul 2015 20:01:07 -0700	[thread overview]
Message-ID: <007801d0cb3d$25ec4870$71c4d950$@codeaurora.org> (raw)

Hi Mark,
We are trying to measure cold start output latency for audio playback
usecase on our platform and observing that the latency is high. As a part of
optimization, we have profiled regcache_sync() API when the codec is out of
reset and observed that regcache_sync() takes little long time for synching
all of the codec registers (around 100 registers). But, the bus connecting
the codec has the capability to send multiple register writes at once. It
seems regmap_multi_reg_write() can be used for triggering multiple register
writes at once. So, we would like to know, if it is possible to use
regmap_multi_reg_write() or a similar function with regcache_sync that
intern calls bus driver's multi_reg_write API to sync to the HW, that will
help in reducing the latency.

Your comments/suggestions are highly appreciated.

Thanks & Regards,
Sudheer
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a
Linux Foundation Collaborative Project

             reply	other threads:[~2015-07-31  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  3:01 Sudheer [this message]
2015-07-31 16:36 ` Using regmap_multi_reg_write() with regcache_sync() Mark Brown

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='007801d0cb3d$25ec4870$71c4d950$@codeaurora.org' \
    --to=spapothi@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgoswami@codeaurora.org \
    --cc=broonie@kernel.org \
    --cc=plai@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.