[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170490259398.18995.11219791852170871212.b4-ty@kernel.org>
Date: Wed, 10 Jan 2024 16:03:13 +0000
From: Mark Brown <broonie@...nel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
matthias.bgg@...il.com, u.kleine-koenig@...gutronix.de,
kuninori.morimoto.gx@...esas.com, trevor.wu@...iatek.com,
jernej.skrabec@...il.com, claudiu.beznea@...on.dev, robh@...nel.org,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt8195: Remove afe-dai component and
rework codec link
On Wed, 10 Jan 2024 11:57:57 +0100, AngeloGioacchino Del Regno wrote:
> Remove the extra 'mt8195-afe-pcm-dai' component, register the DAI
> drivers to the main AFE component, and rework the DAI linking between
> the headset codec (RT5682/RT5682S) and the TDM interface in the probe
> function to stop assigning name, relying on the of_node of the codec.
> Also replace the COMP_DUMMY codec entry with a COMP_EMPTY for the
> ETDM2_IN and remove it entirely from ETDM1_OUT to fix the registration
> flow for this sound card.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: mediatek: mt8195: Remove afe-dai component and rework codec link
commit: e70b8dd26711704b1ff1f1b4eb3d048ba69e29da
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
Powered by blists - more mailing lists