1. 15 12月, 2016 3 次提交
  2. 04 11月, 2016 2 次提交
  3. 29 10月, 2016 1 次提交
    • D
      ASoC: Intel: Skylake: Use DPIB to update position for Playback stream · ca590c1c
      Dharageswari R 提交于
      DPIB is read currently from a buffer position in memory (indicated by
      the registers DPIB[U|L]BASE).Driver reads the position buffer on BDL
      completion interrupts to report the DMA position. But the BDL completion
      interrupt only indicates the last DMA transfer of the buffer is
      completed at the Intel HD Audio subsystem boundary. The periodic DMA
      Position-in-Buffer writes may be scheduled at the same time or later
      than the MSI and does not guarantee to reflect the position of the last
      buffer that was transferred.
      
      Whereas DPIB register in HDA space(vendor specific register indicated by
      SDxDPIB) reflects the actual data that is transferred. Hence update the
      position based on DPIB for playback.
      Signed-off-by: NDharageswari R <dharageswari.r@intel.com>
      Signed-off-by: NJeeja KP <jeeja.kp@intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      ca590c1c
  4. 06 10月, 2016 1 次提交
    • D
      ASoC: Intel: Skylake: Use DPIB to update position for Playback stream · 9a58725b
      Dharageswari R 提交于
      DPIB is read currently from a buffer position in memory (indicated by
      the registers DPIB[U|L]BASE).Driver reads the position buffer on BDL
      completion interrupts to report the DMA position. But the BDL completion
      interrupt only indicates the last DMA transfer of the buffer is
      completed at the Intel HD Audio subsystem boundary. The periodic DMA
      Position-in-Buffer writes may be scheduled at the same time or later
      than the MSI and does not guarantee to reflect the position of the last
      buffer that was transferred.
      
      Whereas DPIB register in HDA space(vendor specific register indicated by
      SDxDPIB) reflects the actual data that is transferred. Hence update the
      position based on DPIB for playback.
      Signed-off-by: NDharageswari R <dharageswari.r@intel.com>
      Signed-off-by: NJeeja KP <jeeja.kp@intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      9a58725b
  5. 15 9月, 2016 1 次提交
  6. 13 9月, 2016 1 次提交
    • J
      ASoC: constify snd_pcm_ops structures · 115c7254
      Julia Lawall 提交于
      Check for snd_pcm_ops structures that are only stored in the ops field of a
      snd_soc_platform_driver structure or passed as the third argument to
      snd_pcm_set_ops.  The corresponding field or parameter is declared const,
      so snd_pcm_ops structures that have this property can be declared as const
      also.
      
      The semantic patch that makes this change is as follows:
      (http://coccinelle.lip6.fr/)
      
      // <smpl>
      @r disable optional_qualifier@
      identifier i;
      position p;
      @@
      static struct snd_pcm_ops i@p = { ... };
      
      @ok1@
      identifier r.i;
      struct snd_soc_platform_driver e;
      position p;
      @@
      e.ops = &i@p;
      
      @ok2@
      identifier r.i;
      expression e1, e2;
      position p;
      @@
      snd_pcm_set_ops(e1, e2, &i@p)
      
      @bad@
      position p != {r.p,ok1.p,ok2.p};
      identifier r.i;
      struct snd_pcm_ops e;
      @@
      e@i@p
      
      @depends on !bad disable optional_qualifier@
      identifier r.i;
      @@
      static
      +const
       struct snd_pcm_ops i = { ... };
      // </smpl>
      Signed-off-by: NJulia Lawall <Julia.Lawall@lip6.fr>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      115c7254
  7. 02 9月, 2016 1 次提交
  8. 11 8月, 2016 1 次提交
  9. 09 8月, 2016 1 次提交
  10. 08 8月, 2016 1 次提交
  11. 07 6月, 2016 3 次提交
  12. 13 5月, 2016 1 次提交
  13. 11 5月, 2016 1 次提交
  14. 02 5月, 2016 2 次提交
  15. 29 4月, 2016 1 次提交
  16. 19 2月, 2016 2 次提交
  17. 09 2月, 2016 2 次提交
  18. 04 2月, 2016 1 次提交
  19. 10 1月, 2016 4 次提交
  20. 09 12月, 2015 1 次提交
  21. 02 12月, 2015 1 次提交
  22. 26 11月, 2015 2 次提交
  23. 19 11月, 2015 2 次提交
  24. 16 11月, 2015 4 次提交