1. 27 6月, 2018 1 次提交
  2. 31 5月, 2018 1 次提交
    • H
      ASoC: Intel: bytcr_rt5651: Set card long_name based on quirks · 64484cce
      Hans de Goede 提交于
      Many X86 devices using a BYT SoC + RT5651 codec are cheap devices with
      generic DMI strings, causing snd_soc_set_dmi_name() to fail to set a
      long_name, making it impossible for userspace to have a correct UCM
      profile which knowns which input is connected to the internal mic,
      which input is connected to the hsmic (for correct jack-based switching)
      and which inputs are unused.
      
      Our quirks already specify which inputs the internal and headset mic
      are connected to.
      
      This commit sets a long_name based on the quirks so that userspace can
      have UCM profiles doing the right thing based on the long_name.
      
      Note that if we ever encounter the need for a special UCM profile for
      some device we can add a quirk to set a specific long_name for the
      device,
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      64484cce
  3. 03 5月, 2018 1 次提交
  4. 21 4月, 2018 1 次提交
  5. 28 3月, 2018 1 次提交
  6. 07 3月, 2018 13 次提交
  7. 02 3月, 2018 1 次提交
  8. 12 2月, 2018 1 次提交
  9. 13 1月, 2018 2 次提交
  10. 09 1月, 2018 4 次提交
  11. 29 11月, 2017 2 次提交
  12. 26 10月, 2017 2 次提交
  13. 21 10月, 2017 2 次提交
  14. 18 10月, 2017 4 次提交
  15. 19 9月, 2017 1 次提交
  16. 14 6月, 2017 1 次提交
  17. 25 4月, 2017 1 次提交
    • T
      ASoC: intel: Fix PM and non-atomic crash in bytcr drivers · 6e4cac23
      Takashi Iwai 提交于
      The FE setups of Intel SST bytcr_rt5640 and bytcr_rt5651 drivers carry
      the ignore_suspend flag, and this prevents the suspend/resume working
      properly while the stream is running, since SST core code has the
      check of the running streams and returns -EBUSY.  Drop these
      superfluous flags for fixing the behavior.
      
      Also, the bytcr_rt5640 driver lacks of nonatomic flag in some FE
      definitions, which leads to the kernel Oops at suspend/resume like:
      
        BUG: scheduling while atomic: systemd-sleep/3144/0x00000003
        Call Trace:
         dump_stack+0x5c/0x7a
         __schedule_bug+0x55/0x70
         __schedule+0x63c/0x8c0
         schedule+0x3d/0x90
         schedule_timeout+0x16b/0x320
         ? del_timer_sync+0x50/0x50
         ? sst_wait_timeout+0xa9/0x170 [snd_intel_sst_core]
         ? sst_wait_timeout+0xa9/0x170 [snd_intel_sst_core]
         ? remove_wait_queue+0x60/0x60
         ? sst_prepare_and_post_msg+0x275/0x960 [snd_intel_sst_core]
         ? sst_pause_stream+0x9b/0x110 [snd_intel_sst_core]
         ....
      
      This patch addresses these appropriately, too.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Acked-by: NVinod Koul <vinod.koul@intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      Cc: <stable@vger.kernel.org> # v4.1+
      6e4cac23
  18. 01 2月, 2017 1 次提交