1. 17 4月, 2013 2 次提交
  2. 04 4月, 2013 2 次提交
  3. 26 3月, 2013 1 次提交
  4. 05 3月, 2013 1 次提交
  5. 29 1月, 2013 2 次提交
  6. 24 1月, 2013 4 次提交
  7. 17 1月, 2013 1 次提交
  8. 14 1月, 2013 1 次提交
  9. 25 12月, 2012 1 次提交
  10. 24 12月, 2012 1 次提交
  11. 09 12月, 2012 1 次提交
  12. 20 11月, 2012 1 次提交
  13. 06 11月, 2012 1 次提交
    • S
      ARM: tegra: remove <mach/dma.h> · 8a5d51fd
      Stephen Warren 提交于
      Remove includes of <mach/dma.h> from sound/soc; nothing from it is used.
      
      Remove include of <mach/dma.h> from mach-tegra/apbio.c; since the DMA
      transfers made by this file don't need flow-control with any peripheral,
      there's no need to set any slave ID.
      
      Once those changes are made, there are no remaining users of <mach/dma.h>
      so remove it. Drivers should get this information from device tree. This
      removal is necessary for single zImage.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Acked-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      8a5d51fd
  14. 17 9月, 2012 1 次提交
  15. 07 9月, 2012 1 次提交
  16. 06 9月, 2012 1 次提交
  17. 29 8月, 2012 1 次提交
  18. 27 7月, 2012 2 次提交
  19. 04 7月, 2012 1 次提交
  20. 13 6月, 2012 1 次提交
  21. 12 6月, 2012 2 次提交
  22. 08 6月, 2012 6 次提交
  23. 03 6月, 2012 5 次提交
    • S
      ASoC: make snd_soc_dai_link more symmetrical · bc92657a
      Stephen Warren 提交于
      Prior to this patch, the CPU side of a DAI link was specified using a
      single name. Often, this was the result of calling dev_name() on the
      device providing the DAI, but in the case of a CPU DAI driver that
      provided multiple DAIs, it needed to mix together both the device name
      and some device-relative name, in order to form a single globally unique
      name.
      
      However, the CODEC side of the DAI link was specified using separate
      fields for device (name or OF node) and device-relative DAI name.
      
      This patch allows the CPU side of a DAI link to be specified in the same
      way as the CODEC side, separating concepts of device and device-relative
      DAI name.
      
      I believe this will be important in multi-codec and/or dynamic PCM
      scenarios, where a single CPU driver provides multiple DAIs, while also
      booting using device tree, with accompanying desire not to hard-code the
      CPU side device's name into the original .cpu_dai_name field.
      
      Ideally, both the CPU DAI and CODEC DAI loops in soc_bind_dai_link()
      would now be identical. However, two things prevent that at present:
      
      1) The need to save rtd->codec for the CODEC side, which means we have
      to search for the CODEC explicitly, and not just the CODEC side DAI.
      
      2) Since we know the CODEC side DAI is part of a codec, and not just
      a standalone DAI, it's slightly more efficient to convert .codec_name/
      .codec_of_node into a codec first, and then compare each DAI's .codec
      field, since this avoids strcmp() on each DAI's CODEC's name within
      the loop.
      
      However, the two loops are essentially semantically equivalent.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      bc92657a
    • S
      ASoC: tegra+wm8903: remove non-DT support for Seaboard · b350ecbe
      Stephen Warren 提交于
      In kernel 3.6, Seaboard will only be supported when booting using device
      tree; the board files are being removed. Hence, remove the non-DT support
      for Seaboard and derivatives Kaen and Aebl from the audio driver.
      
      Harmony is the only remaining board supported by this driver when not
      using DT. This support is currently scheduled for removal in 3.7.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      b350ecbe
    • S
      ASoC: tegra+wm8903: simplify gpio tests in widget callbacks · 14df415a
      Stephen Warren 提交于
      By the time any widget callbacks could be called, if the GPIO ID they
      will manipulate is valid, it must have already been requested, or the
      card would have failed to probe or initialize. So, testing for GPIO
      validity is equivalent to testing whether the GPIO was successfully
      requested at this point in the code. Making this change will allow later
      patches to remove the gpio_requested variable.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      14df415a
    • S
      ASoC: tegra+alc5632: unconditionally free jack GPIOs in remove · 9f6328d9
      Stephen Warren 提交于
      The headphone jack GPIOs are added/initialized in the DAI link's init()
      method, and hence in theory may not always have been added before remove()
      is called in some unusual cases. In order to prevent calling
      snd_soc_jack_free_gpios() if snd_soc_jack_add_gpios() had not been, the
      code kept track of the initialization state to avoid the free call when
      necessary.
      
      However, it appears that snd_soc_jack_free_gpios() is robust in the face
      of being called without snd_soc_jack_add_gpios() first succeeding, so
      there is little point manually tracking this information. Hence, remove
      the tracking code. All other machine drivers already operate this way.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      9f6328d9
    • S
      ASoC: tegra+alc5632: move all GPIO setup into probe · aef9a37c
      Stephen Warren 提交于
      Now that deferred probe exists, we can parse device tree and request
      GPIOs from probe(), rather than deferring this to the DAI link's init().
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      aef9a37c