1. 13 3月, 2013 1 次提交
  2. 28 9月, 2012 1 次提交
  3. 23 8月, 2012 3 次提交
  4. 04 8月, 2012 3 次提交
  5. 03 6月, 2012 1 次提交
  6. 02 5月, 2012 1 次提交
  7. 28 4月, 2012 3 次提交
    • M
      ASoC: wm_hubs: Enable class W for output mixer paths · 04de57c1
      Mark Brown 提交于
      Class W can be used for any path where only data from the DAC is routed
      to the headphones. Currently we only enable it when the direct DAC to
      headphone path is used but it can also be enabled for paths that go via
      the output mixer providing the DAC is the only input to the output mixer.
      Implement support for this, including updates to the class W status when
      the output mixer configuration is changed. This also allows us to enable
      the DC servo optimisations for DAC to headphone paths where the output
      mixer is used.
      
      In general the direct DAC path is still preferred as this will offer
      better performance on most wm_hubs devices but these additional paths
      can simplify use case management.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      04de57c1
    • M
      ASoC: wm_hubs: Factor out class W management · c340304d
      Mark Brown 提交于
      Since the analogue portions of the checks for class W are the same over
      all the devices factor out these checks into wm_hubs and while we're at
      it also use wm_hubs_dac_hp_direct() to enable class W optimisations on
      more paths.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c340304d
    • M
      ASoC: wm_hubs: Special case headphones for digital paths in more use cases · af31a227
      Mark Brown 提交于
      The optimisations which we can do with caching the headphone DCS result in
      wm_hubs have only been enabled in cases where class W is enabled. However,
      there are more use cases which can benefit from the cache, especially with
      WM8994 series devices with their more advanced digital routing.
      
      Rather than keying off the class W information from the CODECs have a
      check in wm_hubs for a suitable path and use that to determine if we can
      deploy our headphone optimisations.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      af31a227
  8. 24 4月, 2012 1 次提交
  9. 20 3月, 2012 1 次提交
  10. 04 3月, 2012 1 次提交
  11. 01 3月, 2012 1 次提交
  12. 21 2月, 2012 1 次提交
  13. 12 2月, 2012 2 次提交
  14. 08 2月, 2012 1 次提交
  15. 04 2月, 2012 1 次提交
    • L
      ASoC: core: Add support for DAI and machine kcontrols. · 022658be
      Liam Girdwood 提交于
      Currently ASoC can only add kcontrols using codec and platform component device
      handles. It's also desirable to add kcontrols for DAIs (i.e. McBSP) and for
      SoC card machine drivers too. This allows the kcontrol to have a direct handle to
      the parent ASoC component DAI/SoC Card/Platform/Codec device and hence easily
      get it's private data.
      
      This change makes snd_soc_add_controls() static and wraps it in the folowing
      calls (card and dai are new) :-
      
      snd_soc_add_card_controls()
      snd_soc_add_codec_controls()
      snd_soc_add_dai_controls()
      snd_soc_add_platform_controls()
      
      This patch also does a lot of small mechanical changes in individual codec drivers
      to replace snd_soc_add_controls() with snd_soc_add_codec_controls().
      
      It also updates the McBSP DAI driver to use snd_soc_add_dai_controls().
      
      Finally, it updates the existing machine drivers that register controls to either :-
      
      1) Use snd_soc_add_card_controls() where no direct codec control is required.
      2) Use snd_soc_add_codec_controls() where there is direct codec control.
      
      In the case of 1) above we also update the machine drivers to get the correct
      component data pointers from the kcontrol (rather than getting the machine pointer
      via the codec pointer).
      Signed-off-by: NLiam Girdwood <lrg@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      022658be
  16. 02 2月, 2012 1 次提交
  17. 01 2月, 2012 1 次提交
  18. 31 1月, 2012 1 次提交
  19. 28 1月, 2012 1 次提交
  20. 27 1月, 2012 1 次提交
  21. 03 12月, 2011 1 次提交
  22. 27 11月, 2011 1 次提交
  23. 20 11月, 2011 1 次提交
  24. 05 11月, 2011 1 次提交
  25. 06 10月, 2011 2 次提交
  26. 14 8月, 2011 1 次提交
  27. 01 8月, 2011 2 次提交
  28. 29 7月, 2011 1 次提交
  29. 15 7月, 2011 1 次提交
  30. 13 7月, 2011 2 次提交