1. 04 1月, 2020 1 次提交
  2. 30 12月, 2019 1 次提交
  3. 29 12月, 2019 1 次提交
  4. 27 12月, 2019 1 次提交
  5. 24 12月, 2019 1 次提交
    • T
      ALSA: hda - Apply sync-write workaround to old Intel platforms, too · c366b3db
      Takashi Iwai 提交于
      Klaus Ethgen reported occasional high CPU usages in his system that
      seem caused by HD-audio driver.  The perf output revealed that it's
      in the unsolicited event handling in the workqueue, and the problem
      seems triggered by some communication stall between the controller and
      the codec at the runtime or system resume.
      
      Actually a similar phenomenon was seen in the past for other Intel
      platforms, and we already applied the workaround to enforce sync-write
      for CORB/RIRB verbs for Skylake and newer chipsets (commit
      2756d914 "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel
      chips").  Fortunately, the same workaround is applicable to the old
      chipset, and the experiment showed the positive effect.
      
      Based on the experiment result, this patch enables the sync-write
      workaround for all Intel chipsets.  The only reason I hesitated to
      apply this workaround was about the possibly slightly higher CPU usage.
      But if the lack of sync causes a much severer problem even for quite
      old chip, we should think this would be necessary for all Intel chips.
      Reported-by: NKlaus Ethgen <Klaus@ethgen.ch>
      Cc: <stable@vger.kernel.org>
      Link: https://lore.kernel.org/r/20191223171833.GA17053@chua
      Link: https://lore.kernel.org/r/20191223221816.32572-1-tiwai@suse.deSigned-off-by: NTakashi Iwai <tiwai@suse.de>
      c366b3db
  6. 21 12月, 2019 1 次提交
  7. 20 12月, 2019 1 次提交
  8. 19 12月, 2019 2 次提交
  9. 17 12月, 2019 1 次提交
  10. 16 12月, 2019 2 次提交
  11. 15 12月, 2019 5 次提交
  12. 11 12月, 2019 2 次提交
  13. 10 12月, 2019 9 次提交
  14. 09 12月, 2019 2 次提交
  15. 08 12月, 2019 1 次提交
    • O
      ALSA: echoaudio: simplify get_audio_levels · c08f0a92
      Olof Johansson 提交于
      The loop optimizer seems to go astray here, and produces some warnings
      that don't seem valid.
      
      Still, the code can be simplified -- just clear the whole array at the
      beginning, and fill in whatever values are valid on the platform.
      
      Warnings before this change (GCC 8.2.0 ARM allmodconfig):
      
      In file included from ../sound/pci/echoaudio/gina24.c:115:
      ../sound/pci/echoaudio/echoaudio.c: In function 'snd_echo_vumeters_get':
      ../sound/pci/echoaudio/echoaudio_dsp.c:647:9: warning: iteration 1073741824 invokes undefined behavior [-Waggressive-loop-optimizations]
      In file included from ../sound/pci/echoaudio/layla24.c:112:
      ../sound/pci/echoaudio/echoaudio.c: In function 'snd_echo_vumeters_get':
      ../sound/pci/echoaudio/echoaudio_dsp.c:658:9: warning: iteration 1073741824 invokes undefined behavior [-Waggressive-loop-optimizations]
      ../sound/pci/echoaudio/echoaudio_dsp.c:647:9: warning: iteration 1073741824 invokes undefined behavior [-Waggressive-loop-optimizations]
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      Link: https://lore.kernel.org/r/20191207224953.25944-1-olof@lixom.netSigned-off-by: NTakashi Iwai <tiwai@suse.de>
      c08f0a92
  16. 04 12月, 2019 4 次提交
  17. 03 12月, 2019 2 次提交
  18. 29 11月, 2019 3 次提交