[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168598623165.103672.7353425800916087713.b4-ty@kernel.org>
Date: Mon, 05 Jun 2023 18:30:31 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, tiwai@...e.com, perex@...ex.cz,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com,
Trevor Wu <trevor.wu@...iatek.com>
Cc: amergnat@...libre.com, alsa-devel@...a-project.org,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/7] ASoC: mt8188: add new board support
On Fri, 26 May 2023 17:31:43 +0800, Trevor Wu wrote:
> In the series, we extend the capability of mt8188-mt6359 driver.
>
> The following changes are included.
> 1. Divide ADDA BE dai into two dais for SOF.
> 2. Register hdmi/dp jack pins.
> 3. dai_fmt can be configured from device tree.
> 4. Add some I2S codecs support.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: mediatek: mt8188: separate ADDA playback dai from capture dai
commit: 2a7a1ae95c84d4199736872bfbc39d01f4b6b0ab
[2/7] ASoC: dt-bindings: mediatek,mt8188-mt6359: remove ADDA_BE from link-name
commit: 9fba0d3ec0a074d1a7c094b2cb722f135215fab0
[3/7] ASoC: mediatek: mt8188-mt6359: register hdmi/dp jack pins
commit: 73cf2b3f2b45fa4c231e8e84ae5d8cc80947d799
[4/7] ASoC: mediatek: common: soundcard driver add dai_fmt support
commit: c0e7390e6d3f42b9a15a0e72add21facb8e17790
[5/7] ASoC: soc-dapm.c: clean up debugfs for freed widget
commit: 8ad13cdc92f66333ae475251ae7722313f84e496
[6/7] ASoC: mediatek: mt8188-mt6359: support new board with nau88255
commit: 9f08dcbddeb307793bbfff036db213d2cdf03a50
[7/7] ASoC: dt-bindings: mediatek,mt8188-mt6359: add NAU8825 support
commit: ee02b869dcad7ba3772b58e93dd90ab4f932fac5
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