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 0/3] ASoC: Extend DAPM to handle cross-device paths
Date: Fri, 12 Nov 2010 11:23:23 +0200 [thread overview]
Message-ID: <1289553806-28625-1-git-send-email-jhnikula@gmail.com> (raw)
Hi
Here's updated version of previous RFC_ii/iv set:
http://mailman.alsa-project.org/pipermail/alsa-devel/2010-October/033196.html
Patches 1-2 have no remarkable changes, just modified on top of recent changes.
Patch 3 is simpler as it turns out that the dapm_seq_run_coalesced doesn't need
any changes because it's enough to call it with a right DAPM context.
One fix is in beginning of dapm_power_widgets that d->dev_power is zeroed only
for those codecs that have widgets in order to avoid unnecessary widgetless
codec bias shutdowns.
Minor changes are dapm.sys_power renaming to dev_power and long lines are cut.
--
Jarkko
next reply other threads:[~2010-11-12 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 9:23 Jarkko Nikula [this message]
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
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=1289553806-28625-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;
as well as URLs for NNTP newsgroup(s).