Skip to content
Snippets Groups Projects
  1. Sep 13, 2021
  2. Sep 10, 2021
  3. Sep 09, 2021
  4. Sep 07, 2021
  5. Sep 03, 2021
  6. Sep 01, 2021
  7. Aug 30, 2021
  8. Aug 29, 2021
  9. Aug 27, 2021
  10. Aug 26, 2021
    • 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
    • Pierre-Louis Bossart's avatar
      ASoC: soc-pcm: protect BE dailink state changes in trigger · 0c75fc71
      Pierre-Louis Bossart authored
      
      When more than one FE is connected to a BE, e.g. in a mixing use case,
      the BE can be triggered multiple times when the FE are opened/started
      concurrently. This race condition is problematic in the case of
      SoundWire BE dailinks, and this is not desirable in a general
      case. The code carefully checks when the BE can be stopped or
      hw_free'ed, but the trigger code does not use any mutual exclusion.
      
      Fix by using the same spinlock already used to check FE states, and
      set the state before the trigger. In case of errors,  the initial
      state will be restored.
      
      This patch does not change how the triggers are handled, it only makes
      sure the states are handled in critical sections.
      
      Signed-off-by: default avatarPierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
      Message-Id: <20210817164054.250028-2-pierre-louis.bossart@linux.intel.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      0c75fc71
    • Christophe JAILLET's avatar
      ASoC: wcd9335: Disable irq on slave ports in the remove function · d3efd26a
      Christophe JAILLET authored
      
      The probe calls 'wcd9335_setup_irqs()' to enable interrupts on all slave
      ports.
      This must be undone in the remove function.
      
      Add a 'wcd9335_teardown_irqs()' function that undoes 'wcd9335_setup_irqs()'
      function, and call it from the remove function.
      
      Fixes: 20aedafd ("ASoC: wcd9335: add support to wcd9335 codec")
      Signed-off-by: default avatarChristophe JAILLET <christophe.jaillet@wanadoo.fr>
      Message-Id: <8f761244d79bd4c098af8a482be9121d3a486d1b.1629091028.git.christophe.jaillet@wanadoo.fr>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      d3efd26a
    • Christophe JAILLET's avatar
      ASoC: wcd9335: Fix a memory leak in the error handling path of the probe function · fc6fc81c
      Christophe JAILLET authored
      
      If 'wcd9335_setup_irqs()' fails, me must release the memory allocated in
      'wcd_clsh_ctrl_alloc()', as already done in the remove function.
      
      Add an error handling path and the missing 'wcd_clsh_ctrl_free()' call.
      
      Fixes: 20aedafd ("ASoC: wcd9335: add support to wcd9335 codec")
      Signed-off-by: default avatarChristophe JAILLET <christophe.jaillet@wanadoo.fr>
      Message-Id: <6dc12372f09fabb70bf05941dbe6a1382dc93e43.1629091028.git.christophe.jaillet@wanadoo.fr>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      fc6fc81c
    • Christophe JAILLET's avatar
      ASoC: wcd9335: Fix a double irq free in the remove function · 7a6a723e
      Christophe JAILLET authored
      
      There is no point in calling 'free_irq()' explicitly for
      'WCD9335_IRQ_SLIMBUS' in the remove function.
      
      The irqs are requested in 'wcd9335_setup_irqs()' using a resource managed
      function (i.e. 'devm_request_threaded_irq()').
      'wcd9335_setup_irqs()' requests all what is defined in the 'wcd9335_irqs'
      structure.
      This structure has only one entry for 'WCD9335_IRQ_SLIMBUS'.
      
      So 'devm_request...irq()' + explicit 'free_irq()' would lead to a double
      free.
      
      Remove the unneeded 'free_irq()' from the remove function.
      
      Fixes: 20aedafd ("ASoC: wcd9335: add support to wcd9335 codec")
      Signed-off-by: default avatarChristophe JAILLET <christophe.jaillet@wanadoo.fr>
      Message-Id: <0614d63bc00edd7e81dd367504128f3d84f72efa.1629091028.git.christophe.jaillet@wanadoo.fr>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      7a6a723e
Loading