From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Fix section mismatch in wm8995.c
Date: Wed, 12 Jan 2011 10:46:25 +0000 [thread overview]
Message-ID: <20110112104624.GA20911@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1294826290.11031.15.camel@dplaptop.localdomain>
On Wed, Jan 12, 2011 at 09:58:10AM +0000, Dimitris Papastamos wrote:
> On Tue, 2011-01-11 at 18:14 +0000, Mark Brown wrote:
> > That's a bug in the flat cache, it should be stashing a copy of it in
> > the codec instance. Though it only really makes a difference for
> > devices where you'd want to use a compressed cache anyway.
> The flat cache is intentionally *not* making a copy of the defaults
> cache as it makes no difference in terms of memory usage. The flat
> cache has codec->reg_def_copy = NULL; and can work with either NULL
> default caches or filled in.
It can make a difference to memory usage - if multiple CODEC drivers are
built in but only one is in use then if we take a copy all the defaults
can be discared, meaning that we don't need to keep the defaults for the
unused drivers and only keep the defaults for the one that's in use
instead of keeping the defaults for all drivers.
next prev parent reply other threads:[~2011-01-12 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 17:02 Fix section mismatch in wm8995.c Takashi Iwai
2011-01-11 17:10 ` Mark Brown
2011-01-11 17:18 ` Takashi Iwai
2011-01-11 17:28 ` Mark Brown
2011-01-11 17:32 ` Takashi Iwai
2011-01-11 17:33 ` Mark Brown
2011-01-11 17:48 ` Takashi Iwai
2011-01-11 18:14 ` Mark Brown
2011-01-11 19:12 ` Takashi Iwai
2011-01-12 9:58 ` Dimitris Papastamos
2011-01-12 10:46 ` Mark Brown [this message]
2011-01-12 10:50 ` Dimitris Papastamos
2011-01-12 10:00 ` Dimitris Papastamos
2011-01-12 10:03 ` Takashi Iwai
2011-01-12 10:07 ` Dimitris Papastamos
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=20110112104624.GA20911@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--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 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.