linux-kernel - Re: [PATCH] ASoC: es8328: fix route from DAC to output

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: <174042214288.92672.849071469187216884.b4-ty@kernel.org>
Date: Mon, 24 Feb 2025 18:35:42 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Sean Cross <xobs@...agi.com>, 
 Nicolas Frattaroli <nicolas.frattaroli@...labora.com>
Cc: kernel@...labora.com, Mark Brown <broonie@...aro.org>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: es8328: fix route from DAC to output

On Sat, 22 Feb 2025 20:39:57 +0100, Nicolas Frattaroli wrote:
> The ES8328 codec driver, which is also used for the ES8388 chip that
> appears to have an identical register map, claims that the output can
> either take the route from DAC->Mixer->Output or through DAC->Output
> directly. To the best of what I could find, this is not true, and
> creates problems.
> 
> Without DACCONTROL17 bit index 7 set for the left channel, as well as
> DACCONTROL20 bit index 7 set for the right channel, I cannot get any
> analog audio out on Left Out 2 and Right Out 2 respectively, despite the
> DAPM routes claiming that this should be possible. Furthermore, the same
> is the case for Left Out 1 and Right Out 1, showing that those two don't
> have a direct route from DAC to output bypassing the mixer either.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: es8328: fix route from DAC to output
      commit: 5b0c02f9b8acf2a791e531bbc09acae2d51f4f9b

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