From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: ak4642: Add ak4642_fill_cache function
Date: Fri, 25 Jun 2010 11:47:33 +0100 [thread overview]
Message-ID: <1277462853.3123.13.camel@odin> (raw)
In-Reply-To: <w3pvd97k0nb.wl%kuninori.morimoto.gx@renesas.com>
On Fri, 2010-06-25 at 16:54 +0900, Kuninori Morimoto wrote:
> ak4642 driver is used for ak4642/ak4643.
> So, reading real register value is better than using constant value.
>
To be honest, this is only really useful when the codec has some
volatile registers. Forcing I2C reads for all IO will just slow down
the driver.
Does this codec have volatile registers ?
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-06-25 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 7:54 [PATCH] ASoC: ak4642: Add ak4642_fill_cache function Kuninori Morimoto
2010-06-25 10:47 ` Liam Girdwood [this message]
2010-06-25 11:43 ` Mark Brown
2010-06-28 0:37 ` Kuninori Morimoto
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=1277462853.3123.13.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kuninori.morimoto.gx@renesas.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