linux-kernel - Re: [PATCH 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172356077609.62411.17348863586201066528.b4-ty@kernel.org>
Date: Tue, 13 Aug 2024 15:52:56 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, Sunil-kumar.Dommati@....com, 
 Basavaraj.Hiregoudar@....com, venkataprasad.potturu@....com, 
 pierre-louis.bossart@...ux.intel.com, lgirdwood@...il.com, 
 yung-chuan.liao@...ux.intel.com, peter.ujfalusi@...ux.intel.com, 
 ranjani.sridharan@...ux.intel.com, perex@...ex.cz, tiwai@...e.com, 
 cristian.ciocaltea@...labora.com, sound-open-firmware@...a-project.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 kai.vehmanen@...ux.intel.com, Daniel Baluta <daniel.baluta@....com>
Subject: Re: [PATCH 1/2] ASoC: SOF: amd: move iram-dram fence register
 programming sequence

On Mon, 12 Aug 2024 16:35:09 +0530, Vijendar Mukunda wrote:
> As per design, ACP iram-dram fence register sequence should be initiated
> before triggering SHA dma. This ensures that IRAM size will programmed
> correctly before initiaing SHA dma.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence
      commit: c56ba3e44784527fd6efe5eb7a4fa6c9f6969a58
[2/2] ASoC: SOF: amd: Fix for incorrect acp error register offsets
      commit: 897e91e995b338002b00454fd0018af26a098148

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