linux-kernel - Re: [PATCH] ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007

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: <175889100278.84679.9639895115405021343.b4-ty@kernel.org>
Date: Fri, 26 Sep 2025 13:50:02 +0100
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>, Kevin Lu <kevin-lu@...com>, 
 Baojun Xu <baojun.xu@...com>, Liam Girdwood <lgirdwood@...il.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Primoz Fiser <primoz.fiser@...ik.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 upstream@...ts.phytec.de
Subject: Re: [PATCH] ASoC: tlv320aic3x: Fix class-D initialization for
 tlv320aic3007

On Thu, 25 Sep 2025 10:59:29 +0200, Primoz Fiser wrote:
> The problem of having class-D initialization sequence in probe using
> regmap_register_patch() is that it will do hardware register writes
> immediately after being called as it bypasses regcache. Afterwards, in
> aic3x_init() we also perform codec soft reset, rendering class-D init
> sequence pointless. This issue is even more apparent when using reset
> GPIO line, since in that case class-D amplifier initialization fails
> with "Failed to init class D: -5" message as codec is already held in
> reset state after requesting the reset GPIO and hence hardware I/O
> fails with -EIO errno.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007
      commit: 733a763dd8b3ac2858dd238a91bb3a2fdff4739e

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