From: Jarkko Nikula <jhnikula@gmail.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: [PATCHv2.1 0/3] ASoC: Extend DAPM to handle cross-device paths
Date: Tue, 14 Dec 2010 12:18:29 +0200 [thread overview]
Message-ID: <1292321912-24765-1-git-send-email-jhnikula@gmail.com> (raw)
Hi
Just updated set, i.e. no code changes other than updated to current tree and
some comment clarifications.
Last time there were discussion about special n_widgets casing for
non-DAPM codecs. Mark suggested to drop them but they are still here as I
don't want to break boards having non-DAPM codec with bias control and that
casing is trivial to drop when not needed anymore.
--
Jarkko
next reply other threads:[~2010-12-14 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 10:18 Jarkko Nikula [this message]
2010-12-14 10:18 ` [PATCHv2.1 1/3] ASoC: Move DAPM paths from DAPM context to snd_soc_card Jarkko Nikula
2010-12-14 10:18 ` [PATCHv2.1 2/3] ASoC: Move widgets " Jarkko Nikula
2010-12-14 10:18 ` [PATCHv2.1 3/3] ASoC: Extend DAPM to handle power changes on cross-device paths Jarkko Nikula
2010-12-14 15:57 ` [PATCHv2.1 0/3] ASoC: Extend DAPM to handle " Liam Girdwood
2010-12-15 18:14 ` 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=1292321912-24765-1-git-send-email-jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox