1. 07 Oct, 2021 2 commits
  2. 30 Sep, 2021 1 commit
  3. 27 Sep, 2021 2 commits
  4. 21 Sep, 2021 2 commits
  5. 17 Sep, 2021 2 commits
  6. 16 Sep, 2021 2 commits
  7. 15 Sep, 2021 3 commits
  8. 10 Sep, 2021 7 commits
  9. 09 Sep, 2021 3 commits
  10. 03 Sep, 2021 3 commits
  11. 02 Sep, 2021 1 commit
  12. 01 Sep, 2021 7 commits
  13. 30 Aug, 2021 3 commits
  14. 26 Aug, 2021 2 commits
    • Mark Brown's avatar
      Merge series "ASoC: wcd9335: Firx some resources leak in the probe and remove... · 52c64e5f
      Mark Brown authored
      Merge series "ASoC: wcd9335: Firx some resources leak in the probe and remove function" from Christophe JAILLET <christophe.jaillet@wanadoo.fr>:
      
      The first 2 patches are sraightforward and look logical to me.
      
      However, the 3rd one in purely speculative. It is based on the fact that a
      comment states that we enable some irqs on some slave ports. That said, it writes
      0xFF in some registers.
      
      So, I guess that we should disable these irqs when the driver is removed. That
      said, writing 0x00 at the same place looks logical to me.
      
      This cis untested and NOT based on any documentation. Just a blind fix.
      Review with care.
      You'll be warned :)
      
      Christophe JAILLET (3):
        ASoC: wcd9335: Fix a double irq free in the remove function
        ASoC: wcd9335: Fix a memory leak in the error handling path of the
          probe function
        ASoC: wcd9335: Disable irq on slave ports in the remove function
      
       sound/soc/codecs/wcd9335.c | 23 +++++++++++++++++++++--
       1 file changed, 21 insertions(+), 2 deletions(-)
      
      --
      2.30.2
      52c64e5f
    • Pierre-Louis Bossart's avatar
      ASoC: soc-pcm: test refcount before triggering · 6479f758
      Pierre-Louis Bossart authored
      On start/pause_release/resume, when more than one FE is connected to
      the same BE, it's possible that the trigger is sent more than
      once. This is not desirable, we only want to trigger a BE once, which
      is straightforward to implement with a refcount.
      
      For stop/pause/suspend, the problem is more complicated: the check
      implemented in snd_soc_dpcm_can_be_free_stop() may fail due to a
      conceptual deadlock when we trigger the BE before the FE. In this
      case, the FE states have not yet changed, so there are corner cases
      where the TRIGGER_STOP is never sent - the dual case of start where
      multiple triggers might be sent.
      
      This patch suggests an unconditional trigger in all cases, without
      checking the FE states, using a refcount protected by a spinlock.
      Signed-off-by: default avatarPierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
      Message-Id: <20210817164054.250028-3-pierre-louis.bossart@linux.intel.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      6479f758