From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCHv2 2/3] ASoC: Move widgets from DAPM context to snd_soc_card
Date: Fri, 12 Nov 2010 14:40:04 +0000 [thread overview]
Message-ID: <20101112144003.GE17283@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101112155756.bd8a95be.jhnikula@gmail.com>
On Fri, Nov 12, 2010 at 03:57:56PM +0200, Jarkko Nikula wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > If we keep moving stuff into the card it's questionable what the context
> > is buying us...
> DAPM context represent the parent device (codecs currently and other
> devices in someday) and its state so I don't see we'll be removing it in
> near future even now the widgets and paths are moved to card.
Yeah, but as we keep reducing the amount of per-device state we hold
that could eventually go down to zero - we keep on looking at things
and deciding they're better managed over the whole card.
next prev parent reply other threads:[~2010-11-12 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 9:23 [PATCHv2 0/3] ASoC: Extend DAPM to handle cross-device paths Jarkko Nikula
2010-11-12 9:23 ` [PATCHv2 1/3] ASoC: Move DAPM paths from DAPM context to snd_soc_card Jarkko Nikula
2010-11-12 9:23 ` [PATCHv2 2/3] ASoC: Move widgets " Jarkko Nikula
2010-11-12 13:18 ` Mark Brown
2010-11-12 13:57 ` Jarkko Nikula
2010-11-12 14:25 ` Jarkko Nikula
2010-11-12 14:40 ` Mark Brown [this message]
2010-11-12 9:23 ` [PATCHv2 3/3] ASoC: Extend DAPM to handle power changes on cross-device paths Jarkko Nikula
2010-11-12 15:13 ` Mark Brown
2010-11-12 13:51 ` [PATCHv2 0/3] ASoC: Extend DAPM to handle " Mark Brown
2010-11-12 13:54 ` Mark Brown
2010-11-12 14:15 ` Jarkko Nikula
2010-11-12 14:32 ` Mark Brown
2010-11-12 14:07 ` Jarkko Nikula
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=20101112144003.GE17283@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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.