linux-kernel - Re: [PATCH] ASoC: SOF: amd: Fix for acp init 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: <172381933148.65490.13739657424123950336.b4-ty@kernel.org>
Date: Fri, 16 Aug 2024 15:42:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, pierre-louis.bossart@...ux.intel.com, 
 yung-chuan.liao@...ux.intel.com, ranjani.sridharan@...ux.intel.com, 
 lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com, 
 venkataprasad.potturu@....com, cristian.ciocaltea@...labora.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: SOF: amd: Fix for acp init sequence

On Fri, 16 Aug 2024 12:33:28 +0530, Vijendar Mukunda wrote:
> When ACP is not powered on by default, acp power on sequence explicitly
> invoked by programming pgfsm control mask. The existing implementation
> checks the same PGFSM status mask and programs the same PGFSM control mask
> in all ACP variants which breaks acp power on sequence for ACP6.0 and
> ACP6.3 variants. So to fix this issue, update ACP pgfsm control mask and
> status mask based on acp descriptor rev field, which will vary based on
> acp variant.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: amd: Fix for acp init sequence
      commit: a42db293e5983aa1508d12644f23d73f0553b32c

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