1. 13 1月, 2014 1 次提交
  2. 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
  3. 09 1月, 2014 1 次提交
  4. 07 1月, 2014 1 次提交
  5. 31 12月, 2013 2 次提交
  6. 19 12月, 2013 1 次提交
  7. 12 12月, 2013 1 次提交
  8. 10 12月, 2013 5 次提交
  9. 06 12月, 2013 1 次提交
    • T
      net: davinci_emac: Fix platform data handling and make usable for am3517 · dd0df47d
      Tony Lindgren 提交于
      When booted with device tree, we may still have platform data passed
      as auxdata. For am3517 this is needed for passing the interrupt_enable
      and interrupt_disable callbacks that access the omap system control module
      registers. These callback functions will eventually go away when we have
      a separate system control module driver.
      
      Some of the things that are currently passed as platform data we don't need
      to set up as device tree properties as they are always the same on am3517.
      So let's use a new compatible flag for those so we can get those from
      the device tree match data.
      
      Also note that we need to fix setting of phy_dev to NULL instead of an empty
      string as the code later on uses that to find the first phy on the mdio bus.
      This seems to have been caused by 5d69e007 (net: davinci_emac: switch to
      new mdio).
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      dd0df47d
  10. 05 12月, 2013 2 次提交
  11. 03 12月, 2013 9 次提交
  12. 02 12月, 2013 1 次提交
  13. 28 11月, 2013 1 次提交
  14. 27 11月, 2013 1 次提交
    • T
      mmc: omap: Fix I2C dependency and make driver usable with device tree · 9cb238c0
      Tony Lindgren 提交于
      Some features can be configured by the companion I2C chips,
      which may not be available at the probe time. Fix the issue
      by returning -EPROBE_DEFER when the MMC controller slots
      are not configured.
      
      While at it, let's also add minimal device tree support so
      omap24xx platforms can use this driver without legacy mode
      since we claim to support device tree for mach-omap2 based
      systems.
      
      Although adding the minimal device tree support is not strictly
      a fix, it does remove one of the last blockers for dropping a
      bunch of legacy platform data for mach-omap2.
      
      Cc: linux-mmc@vger.kernel.org
      Acked-by: NChris Ball <cjb@laptop.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      9cb238c0
  15. 26 11月, 2013 1 次提交
  16. 19 11月, 2013 1 次提交
  17. 18 11月, 2013 5 次提交
  18. 16 11月, 2013 2 次提交
  19. 15 11月, 2013 3 次提交