Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: stable@vger.kernel.org
Subject: [PATCH stable v6.12 backport 0/2] ASoC: SOF: ipc4/Intel: Library restore firmware functionality
Date: Fri,  2 Oct 2026 13:23:51 +0300	[thread overview]
Message-ID: <20261002102353.26919-1-peter.ujfalusi@linux.intel.com> (raw)

Hi,

Please pick/apply the following patches from mainline to v6.12 stable:
cec49fa47bcc ("ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data")
ace9b3daf2b4 ("ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality")

They apply cleanly and are available since v6.17

Discussion link (user facing the issue on 6.16):
https://github.com/thesofproject/sof/issues/11229

In theory v6.12 could be used on Lunar Lake hardware where the issue happens.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of
    sof_ipc4_fw_data
  ASoC: SOF: ipc4/Intel: Add support for library restore firmware
    functionality

 include/sound/sof/ipc4/header.h  |  2 ++
 sound/soc/sof/intel/hda-loader.c |  7 +++++--
 sound/soc/sof/ipc4-loader.c      |  6 ++++++
 sound/soc/sof/ipc4-priv.h        |  3 +++
 sound/soc/sof/ipc4.c             | 14 ++++++++++++--
 5 files changed, 28 insertions(+), 4 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-10-02 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:23 Peter Ujfalusi [this message]
2026-10-02 10:23 ` [PATCH stable v6.12 backport 1/2] ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data Peter Ujfalusi
2026-10-02 10:23 ` [PATCH stable v6.12 backport 2/2] ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality Peter Ujfalusi
2026-10-02 21:10 ` [PATCH stable v6.12 backport 0/2] ASoC: SOF: ipc4/Intel: Library " Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261002102353.26919-1-peter.ujfalusi@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox