From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, ALSA <alsa-devel@alsa-project.org>,
"Lu, Guanqun" <guanqun.lu@intel.com>,
alan@linux.intel.com
Subject: Re: [PATCH] ASoC: factor out intel_scu_ipc related read/write
Date: Mon, 9 May 2011 09:31:28 +0200 [thread overview]
Message-ID: <20110509073127.GB21967@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1304910863.32447.3.camel@vkoul-udesk3>
On Mon, May 09, 2011 at 08:44:23AM +0530, Koul, Vinod wrote:
> Meanwhile, i am not sure if this is a good idea.
> We can try enabling cache but will it help? Have you tried that on mrst?
The I/O does not force use of a cache, unless you configure a cache size
nothing will be cached.
> The reason for my paranoia is the SCU API, in past it had issues when we
> do block writes it, something which syncing the cache can cause.
> + Alan for his comments...
The cache I/O won't make any difference here. Unless you implement bulk
operations it's not going to magically work out how to do them - you'll
just see repeated single register operations the same as you see if you
implement this directly in your driver. All that will happen is that
the code will be shared between all drivers using the SCU.
prev parent reply other threads:[~2011-05-09 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:43 [PATCH] ASoC: factor out intel_scu_ipc related read/write Lu Guanqun
2011-05-07 13:48 ` Lu Guanqun
2011-05-09 3:14 ` Koul, Vinod
2011-05-09 5:02 ` Lu Guanqun
2011-05-09 7:31 ` 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=20110509073127.GB21967@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=guanqun.lu@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).