Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Oder Chiou <oder_chiou@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	Bard Liao <bardliao@realtek.com>,
	Gustaw Lewandowski <gustaw.lewandowski@intel.com>,
	Flove <flove@realtek.com>
Subject: Re: [PATCH v5] ASoC: add RT286 CODEC driver
Date: Thu, 13 Mar 2014 19:29:02 +0000	[thread overview]
Message-ID: <20140313192902.GL366@sirena.org.uk> (raw)
In-Reply-To: <s5h61nizdj5.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 325 bytes --]

On Thu, Mar 13, 2014 at 09:52:14AM +0100, Takashi Iwai wrote:

> different values for get and set.  And, yet more tricky part is the
> amplifier verbs.  These aren't suitable with regmap caching,
> unfortunately.

We don't really *need* the cache, it just makes it easier to do resume
and gives a bit of a performance boost.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-03-13 19:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  7:11 [PATCH v5] ASoC: add RT286 CODEC driver bardliao
2014-03-12 21:15 ` Lars-Peter Clausen
2014-03-13  5:29   ` Bard Liao
2014-03-13  8:35     ` Lars-Peter Clausen
2014-03-13  8:52       ` Takashi Iwai
2014-03-13 19:29         ` Mark Brown [this message]
2014-03-13 20:04           ` Takashi Iwai
2014-03-13 20:43             ` Mark Brown
2014-03-14  9:38               ` Bard Liao
2014-03-14 10:16                 ` Mark Brown
2014-03-14 19:12 ` Mark Brown
2014-03-18 12:41   ` Bard Liao
2014-03-18 13:01     ` Mark Brown
2014-03-21  5:57       ` Bard Liao
2014-03-21 12:12         ` 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=20140313192902.GL366@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=flove@realtek.com \
    --cc=gustaw.lewandowski@intel.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=tiwai@suse.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