1. 15 8月, 2015 5 次提交
  2. 11 6月, 2015 1 次提交
  3. 25 5月, 2015 1 次提交
  4. 13 5月, 2015 2 次提交
  5. 11 5月, 2015 2 次提交
  6. 08 5月, 2015 1 次提交
  7. 02 5月, 2015 1 次提交
  8. 28 4月, 2015 1 次提交
    • L
      ASoC: dmaengine_pcm: Make FLAG_NO_RESIDUE internal · acde50a7
      Lars-Peter Clausen 提交于
      Whether residue can be reported or not is not a property of the audio
      controller but of the DMA controller. The FLAG_NO_RESIDUE was initially
      added when the DMAengine framework had no support for describing the residue
      reporting capabilities of the controller. Support for this was added quite a
      while ago and recently the DMAengine framework started to complain if a
      driver does not describe its capabilities and a lot of patches have been
      merged that add support for this where it was missing. So it should be safe
      to assume that driver on actively used platforms properly implement the DMA
      capabilities API.
      
      This patch makes the FLAG_NO_RESIDUE internal and no longer allows audio
      controller drivers to manually set the flag. If a DMA driver against
      expectations does not support reporting its capabilities for now the generic
      DMAengine PCM driver will now emit a warning and simply assume that residue
      reporting is not supported. In the future this might be changed to aborting
      with an error.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      acde50a7
  9. 17 4月, 2015 1 次提交
  10. 12 4月, 2015 1 次提交
  11. 11 4月, 2015 1 次提交
  12. 10 4月, 2015 2 次提交
  13. 23 3月, 2015 1 次提交
  14. 12 3月, 2015 1 次提交
    • S
      ASoC: fsl_spdif: fix struct clk pointer comparing · 81efec85
      Shawn Guo 提交于
      Since commit 035a61c3 ("clk: Make clk API return per-user struct clk
      instances"), clk API users can no longer check if two struct clk
      pointers are pointing to the same hardware clock, i.e. struct clk_hw, by
      simply comparing two pointers.  That's because with the per-user clk
      change, a brand new struct clk is created whenever clients try to look
      up the clock by calling clk_get() or sister functions like clk_get_sys()
      and of_clk_get().  This changes the original behavior where the struct
      clk is only created for once when clock driver registers the clock to
      CCF in the first place.  The net change here is before commit
      035a61c3 the struct clk pointer is unique for given hardware
      clock, while after the commit the pointers returned by clk lookup calls
      become different for the same hardware clock.
      
      That said, the struct clk pointer comparing in the code doesn't work any
      more.  Call helper function clk_is_match() instead to fix the problem.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NMichael Turquette <mturquette@linaro.org>
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      81efec85
  15. 05 3月, 2015 4 次提交
  16. 24 2月, 2015 1 次提交
  17. 11 2月, 2015 1 次提交
  18. 15 1月, 2015 6 次提交
  19. 09 1月, 2015 6 次提交
  20. 07 1月, 2015 1 次提交