1. 15 Jul, 2022 6 commits
  2. 14 Jul, 2022 13 commits
  3. 13 Jul, 2022 18 commits
  4. 12 Jul, 2022 3 commits
    • Mark Brown's avatar
      ASoC: SOF: Intel: hda: Correct Firmware State Register use · 4e90651e
      Mark Brown authored
      Merge series from Peter Ujfalusi <peter.ujfalusi@linux.intel.com>:
      
      The FSR (Firmware State Register) holds the ROM state information, it does not
      contain error information.
      The FSR itself is a bit more complicated as well as the state depends on the
      module currently in use.
      
      The error code from ROM or the status code from the firmware is located at the
      next register.
      
      Fix the handling of the FSR in order to provide usable and human readable (in
      most cases) report on the status and error.
      4e90651e
    • Mark Brown's avatar
      Extend ipc stream parameters sent to DSP · 4457fbd6
      Mark Brown authored
      Merge series from Daniel Baluta <daniel.baluta@oss.nxp.com>
      Daniel Baluta <daniel.baluta@nxp.com>:
      
      From: Daniel Baluta <daniel.baluta@nxp.com>
      
      We need a way to send extra parameters to DSP firmware. In order to do
      this, we introduce ext_data array at the end of ipc_stream_params.
      
      With this new addition we can send compress parameters.
      
      This requires SOF ABI bump.
      4457fbd6
    • Mark Brown's avatar
      ASoC: SOF: Intel: Do not process IPC reply before firmware boot · 501935da
      Mark Brown authored
      Merge series from Peter Ujfalusi <peter.ujfalusi@linux.intel.com>:
      
      By mistake a developer managed to create a 'corrupted' IPC4 firmware image which
      loaded fine to the DSP and after boot it sent an IPC reply before we would have
      received the FW_READY message.
      It turned out that the image was an IPC3 firmware and the IPC reply was the IPC3
      FW_READY notification message which got understood as an IPC4 reply message due
      to the difference between the two IPC mechanism.
      
      This caused a NULL pointer dereference since the reply memory will be allocated
      after the FW_READY message.
      
      To make sure this will not bite again, skip any spurious reply messages before
      the FW_READY.
      501935da