1. 27 Apr, 2012 7 commits
  2. 26 Apr, 2012 11 commits
  3. 25 Apr, 2012 5 commits
  4. 23 Apr, 2012 5 commits
  5. 19 Apr, 2012 2 commits
  6. 18 Apr, 2012 2 commits
  7. 17 Apr, 2012 3 commits
  8. 16 Apr, 2012 5 commits
    • Mark Brown's avatar
      ASoC: Use dai_fmt in Speyside · 26e67811
      Mark Brown authored
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      26e67811
    • Mark Brown's avatar
      ASoC: Merge tag 'v3.4-rc3' into for-3.5 · d5efccd5
      Mark Brown authored
      Linux 3.4-rc3 contains a bunch of Tegra changes which are conflicting
      annoyingly with the new development that's going on for Tegra so merge
      it up to resolve those conflicts.
      
      Conflicts:
      	sound/soc/soc-core.c
      	sound/soc/tegra/tegra_i2s.c
      	sound/soc/tegra/tegra_spdif.c
      d5efccd5
    • Fabio Estevam's avatar
      ASoC: soc-dapm: Use '%llx' with 'u64' type. · 516541a0
      Fabio Estevam authored
      Fix the following build warning:
      
      sound/soc/soc-dapm.c: In function 'snd_soc_dai_link_event':
      sound/soc/soc-dapm.c:2913: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'u64'
      
      '%llx' should be used with 'u64' type.
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      516541a0
    • Mark Brown's avatar
      ASoC: core: Support transparent CODEC<->CODEC DAI links · c74184ed
      Mark Brown authored
      Rather than having the user half start a stream but avoid any DMA to
      trigger data flow on links which don't pass through the CPU create a
      DAPM route between the two DAI widgets using a hw_params configuration
      provided by the machine driver with the new 'params' member of the
      dai_link struct.  If no configuration is provided in the dai_link then
      use the old style even for CODEC<->CODEC links to avoid breaking
      systems.
      
      This greatly simplifies the userspace usage of such links, making them
      as simple as analogue connections with the stream configuration being
      completely transparent to them.
      
      This is achieved by defining a new dai_link widget type which is created
      when CODECs are linked and triggering the configuration of the link via
      the normal PCM operations from there.  It is expected that the bias
      level callbacks will be used for clock configuration.
      
      Currently only the DAI format, rate and channel count can be configured
      and currently the only DAI operations which can be called are hw_params
      and digital_mute().  This corresponds well to the majority of CODEC
      drivers which only use other callbacks for constraint setting but there
      is obviously much room for extension here.  We can't simply call
      hw_params() on startup as things like the system clocking configuration
      may change at runtime and in future it will be desirable to offer some
      configurability of the link parameters.
      
      At present we are also restricted to a single DAPM link for the entire
      DAI.  Once we have better support for channel mapping it would also be
      desirable to extend this feature so that we can propagate per-channel
      power state over the link.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: default avatarLiam Girdwood <lrg@ti.com>
      c74184ed
    • Mark Brown's avatar
      ASoC: core: Bind DAIs to CODECs at registration time · 054880fe
      Mark Brown authored
      We should always have a CODEC already there when registering a CODEC DAI
      and for CODEC<->CODEC links a dai_link will have two CODECs so it's much
      simpler to do things at registration time.
      
      This results in a slight change in the error handling for failed CODEC
      DAI registrations but practically speaking these are never supposed to
      fail so there shouldn't be much issue. The change is that we don't fail
      the overall CODEC registration if the DAI registration fails; this seems
      more robust anyway as we may not need to use a given DAI in a particular
      system.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      054880fe