1. 24 10月, 2013 1 次提交
  2. 21 10月, 2013 2 次提交
  3. 20 10月, 2013 1 次提交
    • L
      ASoC: dmaengine-pcm: Add support for querying DMA capabilities · c0de42bf
      Lars-Peter Clausen 提交于
      Currently each platform making use the the generic dmaengine PCM driver still
      needs to provide a custom snd_pcm_hardware struct which specifies the
      capabilities of the DMA controller, e.g. the maximum period size that can be
      supported. This patch adds code which uses the newly introduced
      dma_get_slave_caps() API to query this information from the dmaengine driver.
      The new code path will only be taken if the 'pcm_hardware' field of the
      snd_dmaengine_pcm_config struct is NULL.
      
      The patch also introduces a new 'fifo_size' field to the
      snd_dmaengine_dai_dma_data struct which is used to initialize the
      snd_pcm_hardware 'fifo_size' field and needs to be set by the DAI driver.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      c0de42bf
  4. 18 10月, 2013 2 次提交
  5. 15 10月, 2013 1 次提交
  6. 12 10月, 2013 1 次提交
  7. 07 10月, 2013 1 次提交
  8. 17 9月, 2013 10 次提交
  9. 09 9月, 2013 1 次提交
  10. 01 9月, 2013 1 次提交
  11. 31 8月, 2013 3 次提交
  12. 27 8月, 2013 1 次提交
  13. 20 8月, 2013 1 次提交
  14. 19 8月, 2013 1 次提交
    • T
      ALSA: pcm: Add snd_printd_ratelimit() · bcbb1553
      Tim Gardner 提交于
      Direct calls to printk_limit() will emit log noise even when CONFIG_SND_DEBUG is not
      defined. Add a wrapper macro around printk_limit() that is conditionally defined by
      CONFIG_SND_DEBUG.
      
      Cc: Jaroslav Kysela <perex@perex.cz>
      Cc: Takashi Iwai <tiwai@suse.de>
      Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
      Cc: Lars-Peter Clausen <lars@metafoo.de>
      Cc: Yacine Belkadi <yacine.belkadi.1@gmail.com>
      Signed-off-by: NTim Gardner <tim.gardner@canonical.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      bcbb1553
  15. 18 8月, 2013 1 次提交
  16. 15 8月, 2013 1 次提交
  17. 11 8月, 2013 2 次提交
  18. 07 8月, 2013 3 次提交
  19. 05 8月, 2013 1 次提交
    • L
      ASoC: dapm: Implement mixer input auto-disable · 57295073
      Lars-Peter Clausen 提交于
      Some devices have the problem that if a internal audio signal source is disabled
      the output of the source becomes undefined or goes to a undesired state (E.g.
      DAC output goes to ground instead of VMID). In this case it is necessary, in
      order to avoid unwanted clicks and pops, to disable any mixer input the signal
      feeds into or to active a mute control along the path to the output. Often it is
      still desirable to expose the same mixer input control to userspace, so cerain
      paths can sill be disabled manually. This means we can not use conventional DAPM
      to manage the mixer input control. This patch implements a method for letting
      DAPM overwrite the state of a userspace visible control. I.e. DAPM will disable
      the control if the path on which the control sits becomes inactive. Userspace
      will then only see a cached copy of the controls state. Once DAPM powers the
      path up again it will sync the userspace setting with the hardware and give
      control back to userspace.
      
      To implement this a new widget type is introduced. One widget of this type will
      be created for each DAPM kcontrol which has the auto-disable feature enabled.
      For each path that is controlled by the kcontrol the widget will be connected to
      the source of that path. The new widget type behaves like a supply widget,
      which means it will power up if one of its sinks are powered up and will only
      power down if all of its sinks are powered down. In order to only have the mixer
      input enabled when the source signal is valid the new widget type will be
      disabled before all other widget types and only be enabled after all other
      widget types.
      
      E.g. consider the following simplified example. A DAC is connected to a mixer
      and the mixer has a control to enable or disable the signal from the DAC.
      
                           +-------+
        +-----+            |       |
        | DAC |-----[Ctrl]-| Mixer |
        +-----+       :    |       |
           |          :    +-------+
           |          :
          +-------------+
          | Ctrl widget |
          +-------------+
      
      If the control has the auto-disable feature enabled we'll create a widget for
      the control. This widget is connected to the DAC as it is the source for the
      mixer input. If the DAC powers up the control widget powers up and if the DAC
      powers down the control widget is powered down. As long as the control widget
      is powered down the hardware input control is kept disabled and if it is enabled
      userspace can freely change the control's state.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      57295073
  20. 30 7月, 2013 5 次提交