From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Suppress restore of default register values for rbtree cache sync
Date: Mon, 6 Jun 2011 10:26:12 +0100 [thread overview]
Message-ID: <20110606092612.GA12190@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110606091807.GA18786@opensource.wolfsonmicro.com>
On Mon, Jun 06, 2011 at 10:18:07AM +0100, Dimitris Papastamos wrote:
> There should be a check for reg_def_copy being NULL, the soc-cache code
> is also built around the idea that the driver might not provide a
> register defaults cache at all so this change needs to cope with that.
Hrm, at this point I'm rather inclined to say that if you're using a
fancy cache method you should be providing defaults.
> Also I'd expect the reg_def_copy cache to be freed sooner rather than
> while unregistering the codec, this is not happening at the moment,
> which is wasting significant space. This is the case because it is only
> used during initialization.
That's the bit I was saying at the bottom of the commit message about
putting it into the node itself; since we're currently never freeing it
we can use it but we should really be copying it into the tree. The
memory wasted is a *much* less severe problem than the I/O bandwidth
consumed rewriting the entire register map on every sync.
next prev parent reply other threads:[~2011-06-06 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 15:37 [PATCH] ASoC: Suppress restore of default register values for rbtree cache sync Mark Brown
2011-06-03 16:29 ` Liam Girdwood
2011-06-06 9:18 ` Dimitris Papastamos
2011-06-06 9:26 ` Mark Brown [this message]
2011-06-06 9:29 ` Dimitris Papastamos
2011-06-06 10:39 ` 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=20110606092612.GA12190@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=patches@opensource.wolfsonmicro.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