1. 25 Aug, 2020 3 commits
  2. 24 Aug, 2020 1 commit
  3. 23 Aug, 2020 3 commits
    • Kai-Heng Feng's avatar
      ALSA: usb-audio: Disable autosuspend for Lenovo ThinkStation P620 · 1965c436
      Kai-Heng Feng authored
      If USB autosuspend is enabled, both front and rear panel can no longer
      detect jack insertion.
      
      Enable USB remote wakeup, i.e. needs_remote_wakeup = 1, doesn't help
      either.
      
      So disable USB autosuspend to prevent missing jack detection event.
      Signed-off-by: default avatarKai-Heng Feng <kai.heng.feng@canonical.com>
      Link: https://lore.kernel.org/r/20200823105854.26950-1-kai.heng.feng@canonical.comSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      1965c436
    • Takashi Sakamoto's avatar
      ALSA: firewire-digi00x: exclude Avid Adrenaline from detection · acd46a6b
      Takashi Sakamoto authored
      Avid Adrenaline is reported that ALSA firewire-digi00x driver is bound to.
      However, as long as he investigated, the design of this model is hardly
      similar to the one of Digi 00x family. It's better to exclude the model
      from modalias of ALSA firewire-digi00x driver.
      
      This commit changes device entries so that the model is excluded.
      
      $ python3 crpp < ~/git/am-config-rom/misc/avid-adrenaline.img
                     ROM header and bus information block
                     -----------------------------------------------------------------
      400  04203a9c  bus_info_length 4, crc_length 32, crc 15004
      404  31333934  bus_name "1394"
      408  e064a002  irmc 1, cmc 1, isc 1, bmc 0, cyc_clk_acc 100, max_rec 10 (2048)
      40c  00a07e01  company_id 00a07e     |
      410  00085257  device_id 0100085257  | EUI-64 00a07e0100085257
      
                     root directory
                     -----------------------------------------------------------------
      414  0005d08c  directory_length 5, crc 53388
      418  0300a07e  vendor
      41c  8100000c  --> descriptor leaf at 44c
      420  0c008380  node capabilities
      424  8d000002  --> eui-64 leaf at 42c
      428  d1000004  --> unit directory at 438
      
                     eui-64 leaf at 42c
                     -----------------------------------------------------------------
      42c  0002410f  leaf_length 2, crc 16655
      430  00a07e01  company_id 00a07e     |
      434  00085257  device_id 0100085257  | EUI-64 00a07e0100085257
      
                     unit directory at 438
                     -----------------------------------------------------------------
      438  0004d6c9  directory_length 4, crc 54985
      43c  1200a02d  specifier id: 1394 TA
      440  13014001  version: Vender Unique and AV/C
      444  17000001  model
      448  81000009  --> descriptor leaf at 46c
      
                     descriptor leaf at 44c
                     -----------------------------------------------------------------
      44c  00077205  leaf_length 7, crc 29189
      450  00000000  textual descriptor
      454  00000000  minimal ASCII
      458  41766964  "Avid"
      45c  20546563  " Tec"
      460  686e6f6c  "hnol"
      464  6f677900  "ogy"
      468  00000000
      
                     descriptor leaf at 46c
                     -----------------------------------------------------------------
      46c  000599a5  leaf_length 5, crc 39333
      470  00000000  textual descriptor
      474  00000000  minimal ASCII
      478  41647265  "Adre"
      47c  6e616c69  "nali"
      480  6e650000  "ne"
      Reported-by: default avatarSimon Wood <simon@mungewell.org>
      Fixes: 9edf723f ("ALSA: firewire-digi00x: add skeleton for Digi 002/003 family")
      Cc: <stable@vger.kernel.org> # 4.4+
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20200823075545.56305-1-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      acd46a6b
    • Takashi Sakamoto's avatar
      ALSA; firewire-tascam: exclude Tascam FE-8 from detection · 0bd8bce8
      Takashi Sakamoto authored
      Tascam FE-8 is known to support communication by asynchronous transaction
      only. The support can be implemented in userspace application and
      snd-firewire-ctl-services project has the support. However, ALSA
      firewire-tascam driver is bound to the model.
      
      This commit changes device entries so that the model is excluded. In a
      commit 53b3ffee ("ALSA: firewire-tascam: change device probing
      processing"), I addressed to the concern that version field in
      configuration differs depending on installed firmware. However, as long
      as I checked, the version number is fixed. It's safe to return version
      number back to modalias.
      
      Fixes: 53b3ffee ("ALSA: firewire-tascam: change device probing processing")
      Cc: <stable@vger.kernel.org> # 4.4+
      Signed-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20200823075537.56255-1-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      0bd8bce8
  4. 19 Aug, 2020 3 commits
  5. 17 Aug, 2020 7 commits
  6. 16 Aug, 2020 1 commit
  7. 15 Aug, 2020 1 commit
  8. 14 Aug, 2020 1 commit
  9. 13 Aug, 2020 1 commit
  10. 12 Aug, 2020 2 commits
  11. 11 Aug, 2020 5 commits
  12. 10 Aug, 2020 6 commits
  13. 07 Aug, 2020 1 commit
  14. 06 Aug, 2020 4 commits
  15. 05 Aug, 2020 1 commit
    • Mohan Kumar's avatar
      ALSA: hda/tegra: Add 100us dma stop delay · ed4d0a4a
      Mohan Kumar authored
      Tegra HDA has audio data buffer for upto tens of frames, this buffer
      can help to avoid underflow. HW will keep issuing new data fetch
      request when buffers are not full and current BDL is not done. When SW
      disable DMA RUN bit for a stream, HW can't cancel the already issued data
      fetch request and hence it can't stop DMA. HW has to wait for all issued
      data fetch request get data returned before it stops DMA.
      
      This HW behavior is not in sync with HDA spec which says DMA RUN bit
      should be cleared within 1 audio frame. For Tegra, DMA RUN bit was
      active for more than one audio frame, due to this the timeout in
      snd_hdac_stream_sync function is not helping. When Stream reset set
      and clear happens during DMA RUN bit active state it results in Memory
      Decode error.
      
      Unfortunately, there is no way to detect when these data accesses have
      completed, but testing has shown that a 100us delay between Stream reset
      set and clear operation for Tegra avoids the memory decode error.
      Therefore, adding a 100us dma stop delay.
      Signed-off-by: default avatarMohan Kumar <mkumard@nvidia.com>
      Link: https://lore.kernel.org/r/20200805095221.5476-4-mkumard@nvidia.comSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      ed4d0a4a