From: Bard Liao <bardliao@realtek.com>
To: Mark Brown <broonie@kernel.org>, 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>,
Gustaw Lewandowski <gustaw.lewandowski@intel.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH v5] ASoC: add RT286 CODEC driver
Date: Fri, 14 Mar 2014 09:38:20 +0000 [thread overview]
Message-ID: <ABFD875FF5FB574BA706497D987D48D739CDD9@RTITMBSV03.realtek.com.tw> (raw)
In-Reply-To: <20140313204323.GM366@sirena.org.uk>
> -----Original Message-----
> From: Mark Brown [mailto:broonie@kernel.org]
> Sent: Friday, March 14, 2014 4:43 AM
> To: Takashi Iwai
> Cc: Lars-Peter Clausen; Bard Liao; Oder Chiou; alsa-devel@alsa-project.org;
> lgirdwood@gmail.com; Gustaw Lewandowski; Flove
> Subject: Re: [alsa-devel] [PATCH v5] ASoC: add RT286 CODEC driver
>
> On Thu, Mar 13, 2014 at 09:04:49PM +0100, Takashi Iwai wrote:
> > Mark Brown wrote:
>
> > > We don't really *need* the cache, it just makes it easier to do
> > > resume and gives a bit of a performance boost.
>
> > Well, the caching isn't just a bit. Without caching, you'd have to
> > whip the sound hardware powered up/down at each time querying the
> > current mixer value.
>
> Realistically most hardware can't actually do that - there's a couple of the
> idle_bias_off devices that have built in LDOs which can but it's relatively
> unusual to be able to remove enough power to loose register I/O (and in any
> case you wind up needing to cache the values per control or something in
> order to do system suspend).
Mark,
What's your suggestion of the I/O part of rt286 codec driver?
Can I keep using regmap without using its cache?
Or it is better not using regmap in this driver?
Thanks.
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2014-03-14 9:38 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
2014-03-13 20:04 ` Takashi Iwai
2014-03-13 20:43 ` Mark Brown
2014-03-14 9:38 ` Bard Liao [this message]
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=ABFD875FF5FB574BA706497D987D48D739CDD9@RTITMBSV03.realtek.com.tw \
--to=bardliao@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).