1. 10 2月, 2014 1 次提交
  2. 24 1月, 2014 1 次提交
  3. 13 1月, 2014 1 次提交
  4. 10 1月, 2014 1 次提交
    • N
      ASoC: fsl_esai: Add ESAI CPU DAI driver · 43d24e76
      Nicolin Chen 提交于
      This patch implements a device-tree-only CPU DAI driver for Freescale ESAI
      controller that supports:
      
       - 12 channels playback and 8 channels record.
         [ Some of the inner transmitters and receivers are sharing same group of
           pins. So the maxmium 12 output or 8 input channels are only valid if
           there is no pin conflict occurring to it. ]
      
       - Independent (asynchronous mode) or shared (synchronous mode) transmit and
         receive sections with separate or shared internal/external clocks and frame
         syncs, operating in Master or Slave mode.
         [ Current ALSA seems not to allow CPU DAI drivers to configure DAI format
           separately for PLAYBACK and CAPTURE. So this first version only supports
           the case that uses the same DAI format for both directions. ]
      
       - Various DAI formats: I2S, Left-Justified, Right-Justified, DSP-A and DSP-B.
      
       - Programmable word length (8, 16, 20 or 24bits)
      
       - Flexible selection between system clock or external oscillator as input
         clock source, programmable internal clock divider and frame sync generation.
      Signed-off-by: NNicolin Chen <Guangyu.Chen@freescale.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      43d24e76
  5. 09 1月, 2014 1 次提交
  6. 07 1月, 2014 1 次提交
  7. 31 12月, 2013 2 次提交
  8. 19 12月, 2013 1 次提交
  9. 13 12月, 2013 1 次提交
    • S
      ASoC: tegra: update module reset list for Tegra124 · f1d6ff79
      Stephen Warren 提交于
      Tegra124 adds a number of extra modules into the configlink bus, which
      must be taken out of reset before the bus is used. Update the AHUB
      driver to know about these extra modules (the AHUB HW module hosts the
      configlink bus).
      Based-on-work-by: NArun Shamanna Lakshmi <aruns@nvidia.com>
      Based-on-work-by: NSonghee Baek <sbaek@nvidia.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Acked-by: NMark Brown <broonie@linaro.org>
      ---
      This patch depends on "ASoC: tegra: use reset framework" to compile,
      which is ack'd and slated to go through a (large) topic branch in the
      Tegra tree. So, we can either:
      
      a) Merge that Tegra topic branch into the ASoC tree, then apply this.
         Note that I haven't created the topic branch yet, since I'm still
         waiting for DMA dependencies to be applied.
      
      b) Apply this change to the Tegra tree too. This change isn't directly
         related to the changes in the Tegra tree; it just makes use of the new
         reset controller feature that's introduced there.
      f1d6ff79
  10. 12 12月, 2013 3 次提交
  11. 10 12月, 2013 5 次提交
  12. 05 12月, 2013 2 次提交
  13. 02 12月, 2013 1 次提交
  14. 28 11月, 2013 1 次提交
  15. 26 11月, 2013 1 次提交
  16. 23 10月, 2013 5 次提交
  17. 22 10月, 2013 3 次提交
  18. 21 10月, 2013 1 次提交
  19. 18 9月, 2013 2 次提交
  20. 06 9月, 2013 1 次提交
    • T
      ASoC: kirkwood: change the compatible string of the kirkwood-i2s driver · d098b2f0
      Thomas Petazzoni 提交于
      The compatible string of the kirkwood-i2s driver was chosen as
      "marvell,mvebu-audio". Using such a compatible string is not a good
      idea, since "mvebu" is the name of a large family of SOCs, in which
      new, unknown SOCs will be coming in the future. It is therefore
      impossible to know what will be evolutions of this hardware block in
      the next generations of the SOCs. For this reason, the recommandation
      for compatible strings of on-SOCs devices has always been to use the
      name of the oldest SOC that has the hardware block. New SOCs that have
      an exactly compatible hardware block can reference it using the same
      compatible string. See [1], [2] and [3] for various cases were this
      suggestion was made, including from Rob Herring, a Device Tree binding
      maintainer.
      
      As an example, there are already small differences between current
      generations:
      
       * On Kirkwood, only one interrupt is used for audio.
       * On Dove, two interrupts are used, one for audio data and one for
         error reporting.
      
      In the near future, I'll be adding audio support to Armada 370, which
      allows has the same hardware block (but maybe with minor variants).
      
      Therefore, this patch changes the driver to accept
      "marvell,kirkwood-audio" and "marvell,dove-audio" as compatible
      strings instead of the too-generic "marvell,mvebu-audio". The reason
      for the two different compatible strings is the difference in the
      number of interrupts used by the two SOCs for audio.
      
      This Device Tree binding has never been part of a Linux kernel stable
      release so far, so it can be changed now without breaking backward
      compatibility.
      
      [1] http://lists.infradead.org/pipermail/linux-mtd/2012-March/040417.html
      [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-April/161065.html
      [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-March/087702.htmlSigned-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      d098b2f0
  21. 29 8月, 2013 1 次提交
  22. 23 8月, 2013 1 次提交
  23. 22 8月, 2013 2 次提交
  24. 20 8月, 2013 1 次提交