Re: [PATCH v2] ASoC: cs35l56: Disconnect ASP1 TX sources when ASP1 DAI is hooked up

[Mark Brown <broonie@xxxxxxxxxx>]

On Thu, 13 Jun 2024 14:25:27 +0100, Richard Fitzgerald wrote:
> If the ASP1 DAI is hooked up by the machine driver the ASP TX mixer
> sources should be initialized to disconnected. There aren't currently
> any available products using the ASP so this doesn't affect any
> existing systems.
> 
> The cs35l56 does not have any fixed default for the mixer source
> registers. When the cs35l56 boots, its firmware patches these registers
> to setup a system-specific routing; this is so that Windows can use
> generic SDCA drivers instead of needing knowledge of chip-specific
> registers. The setup varies between end-products, which each have
> customized firmware, and so the default register state varies between
> end-products. It can also change if the firmware on an end-product is
> upgraded - for example if a change was needed to the routing for Windows
> use-cases. It must be emphasized that the settings applied by the
> firmware are not internal magic tuning; they are statically implementing
> use-case setup that on Linux would be done via ALSA controls.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Disconnect ASP1 TX sources when ASP1 DAI is hooked up
      commit: 8af49868e51ed1ba117b74728af12abe1eda82e5

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