1. 13 12月, 2011 1 次提交
  2. 02 12月, 2011 1 次提交
  3. 24 11月, 2011 1 次提交
    • S
      ASoC: Implement fully_routed card property · 1633281b
      Stephen Warren 提交于
      A card is fully routed if the DAPM route table describes all connections on
      the board.
      
      When a card is fully routed, some operations can be automated by the ASoC
      core. The first, and currently only, such operation is described below, and
      implemented by this patch.
      
      Codecs often have a large number of external pins, and not all of these pins
      will be connected on all board designs. Some machine drivers therefore call
      snd_soc_dapm_nc_pin() for all the unused pins, in order to tell the ASoC core
      never to activate them.
      
      However, when a card is fully routed, the information needed to derive the
      set of unused pins is present in card->dapm_routes. In this case, have
      the ASoC core automatically call snd_soc_dapm_nc_pin() for each unused
      codec pin.
      
      This has been tested with soc/tegra/tegra_wm8903.c and soc/tegra/trimslice.c.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      1633281b
  4. 10 11月, 2011 2 次提交
  5. 27 10月, 2011 1 次提交
  6. 15 10月, 2011 1 次提交
  7. 07 10月, 2011 1 次提交
  8. 06 10月, 2011 5 次提交
  9. 04 10月, 2011 3 次提交
  10. 28 9月, 2011 1 次提交
    • M
      ASoC: Allow DAI formats to be specified in the dai_link · 75d9ac46
      Mark Brown 提交于
      For almost all machines the DAI format is a constant, always set to the
      same thing. This means that not only should we normally set it on init
      rather than in hw_params() (where it has been for historical reasons) we
      should also allow users to configure this by setting a variable in the
      dai_link structure. The combination of these two will make many machine
      drivers even more data driven.
      
      Implement a new dai_fmt field in the dai_link doing just that. Since 0 is
      a valid value for many format flags and we need to be able to tell if the
      field is actually set also add one to all the values used to configure
      formats.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      75d9ac46
  11. 21 9月, 2011 2 次提交
    • D
      ASoC: soc-core: symmetry checking for each DAIs separately · 17841020
      Dong Aisheng 提交于
      The orginal code does not cover the case that one DAI such as codec
      may be shared between other two DAIs(CPU).
      When do symmetry checking, altough the codec DAI requires symmetry,
      the two CPU DAIs may still be configured to run on different rates.
      
      We change to check each DAI's state separately instead of only checking
      the dai link to prevent this issue.
      Signed-off-by: NDong Aisheng <b29396@freescale.com>
      Tested-by: NWolfram Sang <w.sang@pengutronix.de>
      Acked-by: NLiam Girdwood <lrg@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      17841020
    • M
      ASoC: Trace and collect statistics for DAPM graph walking · de02d078
      Mark Brown 提交于
      One of the longest standing areas for improvement in ASoC has been the
      DAPM algorithm - it repeats the same checks many times whenever it is run
      and makes no effort to limit the areas of the graph it checks meaning we
      do an awful lot of walks over the full graph. This has never mattered too
      much as the size of the graph has generally been small in relation to the
      size of the devices supported and the speed of CPUs but it is annoying.
      
      In preparation for work on improving this insert a trace point after the
      graph walk has been done. This gives us specific timing information for
      the walk, and in order to give quantifiable (non-benchmark) numbers also
      count every time we check a link or check the power for a widget and report
      those numbers. Substantial changes in the algorithm may require tweaks to
      the stats but they should be useful for simpler things.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      de02d078
  12. 31 8月, 2011 2 次提交
  13. 23 8月, 2011 1 次提交
  14. 08 8月, 2011 2 次提交
  15. 26 7月, 2011 1 次提交
  16. 06 7月, 2011 3 次提交
  17. 05 7月, 2011 1 次提交
  18. 14 6月, 2011 1 次提交
  19. 10 6月, 2011 1 次提交
    • L
      ASoC: core - PCM mutex per rtd · b8c0dab9
      Liam Girdwood 提交于
      In preparation for the new ASoC Dynamic PCM support (AKA DSP support).
      
      The new ASoC Dynamic PCM core allows DAIs to be dynamically re-routed
      at runtime between the PCM device end (or Frontend - FE) and the physical DAI
      (Backend - BE) using regular kcontrols (just like a hardware CODEC routes
      audio in the analog domain). The Dynamic PCM core therefore must be
      able to call PCM operations for both the Frontend and Backend(s) DAIs at
      the same time.
      
      Currently we have a global pcm_mutex that is used to serialise
      the ASoC PCM operations. This patch removes the global mutex
      and adds a mutex per RTD allowing the PCM operations to be reentrant and
      allow control of more than one DAI at at time. e.g. a frontend PCM hw_params()
      could configure multiple backend DAI hw_params() with similar or different
      hw parameters at the same time.
      Signed-off-by: NLiam Girdwood <lrg@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      b8c0dab9
  20. 08 6月, 2011 2 次提交
  21. 07 6月, 2011 2 次提交
  22. 12 5月, 2011 1 次提交
  23. 03 5月, 2011 1 次提交
  24. 28 4月, 2011 1 次提交
  25. 14 4月, 2011 1 次提交
  26. 08 4月, 2011 1 次提交