1. 09 Apr, 2011 2 commits
    • Mark Brown's avatar
      ASoC: Allow DAPM pin operations to match any context · 0d86733c
      Mark Brown authored
      The DAPM pin operations currently require that the specific DAPM context
      that the pin being operated in is contained in be specified. With multi
      component and especially with the addition of a per-card DAPM context
      this isn't ideal as it means that things like disabling unused pins on
      CODECs require looking up the CODEC DAPM context.
      
      Fix this by falling back to matching a widget in any context if there isn't
      a match in the current context. The code isn't ideal currently but will do
      the job.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: default avatarLiam Girdwood <lrg@ti.com>
      0d86733c
    • Mark Brown's avatar
      ASoC: Force all DAPM contexts into the same bias state · 52ba67bf
      Mark Brown authored
      Currently we allow all DAPM contexts to determine their own bias level.
      While this should in general work in most situations and will deliver the
      lowest possible power it causes problems for our integration with the
      card bias level as we're calling the card bias level functions for each
      DAPM context even though they're card wide but don't say which CODEC
      we're calling them for. Mitigate against this by forcing everything to
      be in the same state.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: default avatarLiam Girdwood <lrg@ti.com>
      52ba67bf
  2. 08 Apr, 2011 6 commits
  3. 06 Apr, 2011 11 commits
  4. 05 Apr, 2011 1 commit
  5. 04 Apr, 2011 4 commits
  6. 03 Apr, 2011 7 commits
  7. 30 Mar, 2011 9 commits