1. 28 4月, 2011 1 次提交
  2. 14 4月, 2011 1 次提交
  3. 08 4月, 2011 1 次提交
  4. 27 3月, 2011 4 次提交
  5. 09 3月, 2011 3 次提交
  6. 03 3月, 2011 3 次提交
  7. 19 2月, 2011 2 次提交
  8. 10 2月, 2011 1 次提交
  9. 28 1月, 2011 1 次提交
  10. 27 1月, 2011 5 次提交
  11. 25 1月, 2011 1 次提交
  12. 20 1月, 2011 1 次提交
  13. 19 1月, 2011 1 次提交
  14. 17 1月, 2011 1 次提交
  15. 14 1月, 2011 1 次提交
  16. 13 1月, 2011 3 次提交
  17. 12 1月, 2011 1 次提交
  18. 11 1月, 2011 2 次提交
  19. 16 12月, 2010 3 次提交
    • J
      ASoC: Extend DAPM to handle power changes on cross-device paths · 7be31be8
      Jarkko Nikula 提交于
      Power change event like stream start/stop or kcontrol change in a
      cross-device path originates from one device but codec bias and widget power
      changes must be populated to another devices on that path as well.
      
      This patch modifies the dapm_power_widgets so that all the widgets on a
      sound card are checked for a power change, not just those that are specific
      to originating device. Also bias management is extended to check all the
      devices. Only exception in bias management are widgetless codecs whose bias
      state is changed only if power change is originating from that context.
      
      DAPM context test is added to dapm_seq_run to take care of if power sequence
      extends to an another device which requires separate register writes.
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      7be31be8
    • J
      ASoC: Move widgets from DAPM context to snd_soc_card · 97c866de
      Jarkko Nikula 提交于
      Decoupling widgets from DAPM context is required when extending the ASoC
      core to cross-device paths. Even the list of widgets are now kept in
      struct snd_soc_card, the widget listing in sysfs and debugs remain sorted
      per device.
      
      This patch makes possible to build cross-device paths but does not extend
      yet the DAPM to handle codec bias and widget power changes of an another
      device.
      
      Cross-device paths are registered by listing the widgets from device A in
      a map for device B. In case of conflicting widget names between the devices,
      a uniform name prefix is needed to separate them. See commit ead9b919
      "ASoC: Add optional name_prefix for kcontrol, widget and route names" for
      help.
      
      An example below shows a path that connects MONO out of A into Line In of B:
      
      static const struct snd_soc_dapm_route mapA[] = {
      	{"MONO", NULL, "DAC"},
      };
      
      static const struct snd_soc_dapm_route mapB[] = {
      	{"Line In", NULL, "MONO"},
      };
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      97c866de
    • J
      ASoC: Move DAPM paths from DAPM context to snd_soc_card · 8ddab3f5
      Jarkko Nikula 提交于
      Decoupling DAPM paths from DAPM context is a first prerequisite when
      extending ASoC core to cross-device paths. This patch is almost a nullop and
      does not allow to construct cross-device setup but the path clean-up part in
      dapm_free_widgets is prepared to remove cross-device paths between a device
      being removed and others.
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      8ddab3f5
  20. 09 12月, 2010 1 次提交
  21. 06 12月, 2010 2 次提交
  22. 04 12月, 2010 1 次提交