1. 17 6月, 2022 1 次提交
  2. 12 4月, 2022 1 次提交
  3. 05 3月, 2022 1 次提交
  4. 02 3月, 2022 1 次提交
  5. 07 1月, 2022 1 次提交
  6. 04 8月, 2021 1 次提交
  7. 19 7月, 2021 1 次提交
  8. 12 7月, 2021 1 次提交
  9. 06 7月, 2021 1 次提交
  10. 18 3月, 2021 1 次提交
  11. 15 1月, 2021 1 次提交
  12. 08 1月, 2021 1 次提交
  13. 06 1月, 2020 1 次提交
  14. 11 12月, 2019 2 次提交
  15. 25 10月, 2019 1 次提交
  16. 05 6月, 2019 1 次提交
  17. 04 2月, 2019 1 次提交
  18. 16 1月, 2019 1 次提交
  19. 03 11月, 2018 2 次提交
  20. 28 8月, 2018 1 次提交
  21. 07 8月, 2018 1 次提交
  22. 28 6月, 2018 1 次提交
  23. 28 2月, 2018 2 次提交
    • T
      ALSA: x86: Fix potential crash at error path · c77a6edb
      Takashi Iwai 提交于
      When LPE audio driver gets some error at probing, it may lead to a
      crash because of canceling the pending work in hdmi_lpe_audio_free(),
      since some of ports might be still not initialized.
      
      For assuring the proper free of each port, initialize all ports at the
      beginning of the probe.
      
      Fixes: b4eb0d52 ("ALSA: x86: Split snd_intelhad into card and PCM specific structures")
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      c77a6edb
    • T
      ALSA: x86: Fix missing spinlock and mutex initializations · 35014406
      Takashi Iwai 提交于
      The commit change for supporting the multiple ports moved involved
      some code shuffling, and there the initializations of spinlock and
      mutex in snd_intelhad object were dropped mistakenly.
      
      This patch adds the missing initializations again for each port.
      
      Fixes: b4eb0d52 ("ALSA: x86: Split snd_intelhad into card and PCM specific structures")
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      35014406
  24. 22 2月, 2018 1 次提交
    • T
      ALSA: x86: hdmi: Add single_port option for compatible behavior · 7229b12f
      Takashi Iwai 提交于
      The recent support for the multiple PCM devices allowed user to use
      multiple HDMI/DP outputs, but at the same time, the PCM stream
      assignment has been changed, too.  Due to that, the former PCM#0
      (there was only one stream in the past) is likely assigned to a
      different one (e.g. PCM#2), and it ends up with the regression when
      user sticks with the fixed configuration using the device#0.
      
      Although the multiple monitor support shouldn't matter when user
      deploys the backend like PulseAudio that checks the jack detection
      state, the behavior change isn't always acceptable for some users.
      
      As a mitigation, this patch introduces an option to switch the
      behavior back to the old-good-days: when the new option,
      single_port=1, is passed, the driver creates only a single PCM device,
      and it's assigned to the first connected one, like the earlier
      versions did.  The option is turned off as default still to support
      the multiple monitors.
      
      Fixes: 8a2d6ae1 ("ALSA: x86: Register multiple PCM devices for the LPE audio card")
      Reported-and-tested-by: NHubert Mantel <mantel@metadox.de>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      7229b12f
  25. 01 7月, 2017 1 次提交
  26. 15 5月, 2017 1 次提交
    • V
      drm/i915: Fix runtime PM for LPE audio · 668e3b01
      Ville Syrjälä 提交于
      Not calling pm_runtime_enable() means that runtime PM can't be
      enabled at all via sysfs. So we definitely need to call it
      from somewhere.
      
      Calling it from the driver seems like a bad idea because it
      would have to be paired with a pm_runtime_disable() at driver
      unload time, otherwise the core gets upset. Also if there's
      no LPE audio driver loaded then we couldn't runtime suspend
      i915 either.
      
      So it looks like a better plan is to call it from i915 when
      we register the platform device. That seems to match how
      pci generally does things. I cargo culted the
      pm_runtime_forbid() and pm_runtime_set_active() calls from
      pci as well.
      
      The exposed runtime PM API is massive an thorougly misleading, so
      I don't actually know if this is how you're supposed to use the API
      or not. But it seems to work. I can now runtime suspend i915 again
      with or without the LPE audio driver loaded, and reloading the
      LPE audio driver also seems to work.
      
      Note that powertop won't auto-tune runtime PM for platform devices,
      which is a little annoying. So I'm not sure that leaving runtime
      PM in "on" mode by default is the best choice here. But I've left
      it like that for now at least.
      
      Also remove the comment about there not being much benefit from
      LPE audio runtime PM. Not allowing runtime PM blocks i915 runtime
      PM, which will also block s0ix, and that could have a measurable
      impact on power consumption.
      
      Cc: stable@vger.kernel.org
      Cc: Takashi Iwai <tiwai@suse.de>
      Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
      Fixes: 0b6b524f ("ALSA: x86: Don't enable runtime PM as default")
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Link: http://patchwork.freedesktop.org/patch/msgid/20170427160231.13337-2-ville.syrjala@linux.intel.comReviewed-by: NTakashi Iwai <tiwai@suse.de>
      (cherry picked from commit 183c0035)
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      668e3b01
  27. 09 5月, 2017 1 次提交
  28. 03 5月, 2017 9 次提交
  29. 22 2月, 2017 1 次提交
    • T
      ALSA: x86: Don't enable runtime PM as default · 0b6b524f
      Takashi Iwai 提交于
      Unlike HSW and newer, BYT/CHT devices have no fine control of audio
      power domain in i915 side.  Since there is little gain by runtime PM
      on BYT/CHT, so far, this commit removes the pm_runtime_enable() call
      as default.
      
      User who still wants the runtime PM may adjust the corresponding
      sysfs files (power/control and power/autosuspend_delay_ms)
      appropriately, of course.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      0b6b524f