ASoC: Extend DAPM to handle cross-device paths
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 10 repliesIn review
- v13 patches 5 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ASoC: Move DAPM paths from DAPM context to snd_soc_cardinclude/ include/ sound/ +2 more | +31 | 0 replies | |
| 2/3 | ASoC: Move widgets from DAPM context to snd_soc_cardinclude/ include/ sound/ +2 more | +55 | 4 replies | |
| 3/3 | ASoC: Extend DAPM to handle power changes on cross-device pathsinclude/ include/ sound/ +1 more | +70 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCHv2 0/3] ASoC: Extend DAPM to handle cross-device paths
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.
Signature · 1 line
Jarkko