[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175379750250.39357.9621820715781114394.b4-ty@kernel.org>
Date: Tue, 29 Jul 2025 14:58:22 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Daniel Baluta <daniel.baluta@....com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Vijendar Mukunda <Vijendar.Mukunda@....com>,
Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
Muhammad Usama Anjum <usama.anjum@...labora.com>
Cc: kernel@...labora.com, stable@...r.kernel.org,
Bard Liao <bard.liao@...el.com>, sound-open-firmware@...a-project.org,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] ASoC: SOF: amd: acp-loader: Use GFP_KERNEL for DMA
allocations in resume context
On Sat, 26 Jul 2025 00:02:54 +0500, Muhammad Usama Anjum wrote:
> Replace GFP_ATOMIC with GFP_KERNEL for dma_alloc_coherent() calls. This
> change improves memory allocation reliability during firmware loading,
> particularly during system resume when memory pressure is high. Because
> of using GFP_KERNEL, reclaim can happen which can reduce the probability
> of failure.
>
> Fixes memory allocation failures observed during system resume with
> fragmented memory conditions.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: amd: acp-loader: Use GFP_KERNEL for DMA allocations in resume context
commit: eb3bb145280b6c857a748731a229698e4a7cf37b
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists