linux-kernel - Re: [PATCH] ASoC: tas571x: add separate tas5733 controls

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: <174836356579.104699.8312897041646074055.b4-ty@kernel.org>
Date: Tue, 27 May 2025 17:32:45 +0100
From: Mark Brown <broonie@...nel.org>
To: Kevin Cernekee <cernekee@...omium.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Bram Vlerick <bram.vlerick@...npixelsystems.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 peter@...sgaard.com
Subject: Re: [PATCH] ASoC: tas571x: add separate tas5733 controls

On Tue, 27 May 2025 13:08:49 +0200, Bram Vlerick wrote:
> The controls between the tas5717 and tas5733 should not be shared since
> the biquad and register setup is not identical. For example, writing to
> 0x5c on the tas5717 modifies ch2_bq[10] while on the tas5733 this is
> ch1_cross_bq[3].
> 
> see https://www.ti.com/lit/ds/symlink/tas5733l.pdf and
> https://www.ti.com/lit/ds/symlink/tas5717.pdf for more details on the
> register maps.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas571x: add separate tas5733 controls
      commit: e3de7984e45155888eebbca5a32c1cc5f29fa859

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