linux-kernel - Re: [PATCH] ASoC: mediatek: mt8186: fix AUD_PAD

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: <170387514707.3010118.10483161102893986503.b4-ty@kernel.org>
Date: Fri, 29 Dec 2023 18:39:07 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, linux-mediatek@...ts.infradead.org, 
 Eugen Hristev <eugen.hristev@...labora.com>
Cc: matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com, 
 allen-kh.cheng@...iatek.com, jiaxin.yu@...iatek.com, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 kernel@...labora.com
Subject: Re: [PATCH] ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and
 offset

On Fri, 29 Dec 2023 13:43:42 +0200, Eugen Hristev wrote:
> AUD_PAD_TOP widget's correct register is AFE_AUD_PAD_TOP , and not zero.
> Having a zero as register, it would mean that the `snd_soc_dapm_new_widgets`
> would try to read the register at offset zero when trying to get the power
> status of this widget, which is incorrect.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and offset
      commit: 38744c3fa00109c51076121c2deb4f02e2f09194

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