[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <173766726032.133083.14869968684527769407.b4-ty@kernel.org>
Date: Thu, 23 Jan 2025 21:21:00 +0000
From: Mark Brown <broonie@...nel.org>
To: robh@...nel.org, krzk+dt@...nel.org,
Daniel Baluta <daniel.baluta@....com>
Cc: shawnguo@...nel.org, conor+dt@...nel.org, peng.fan@....com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
lgirdwood@...il.com, peter.ujfalusi@...ux.intel.com,
linux-sound@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH 0/4] Add SOF support for new board revisions
On Wed, 22 Jan 2025 18:35:40 +0200, Daniel Baluta wrote:
> We introduce SOF support for new board revisions for i.MX8MP/QM/QXP
> which wrt audio they replace wm8960 codec with wm8962.
>
> Also add support for cs42888 codec on i.MX8QM/8QXP baseboard.
>
> Patches 1-3 are already merged in linux SOF tree and they can be merged
> via asoc tree.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] dt-bindings: arm: imx: Add board revisions for i.MX8MP, i.MX8QM and i.MX8QXP
commit: 4b24c69af9cd5bd8fe98ab2ddd822d73f5e20a00
[2/4] ASoC: SOF: imx: Add mach entry to select cs42888 topology
commit: 66084793fac9c8b841f65da1809ad0ad398f9f2f
[3/4] ASoC: SOF: imx8: Add entries for new 8QM and 8QXP revisions
commit: a9f54c7fbd2edb28c8d4d812be3d0129167f92d4
[4/4] ASoC: SOF: imx8m: Add entry for new 8M Plus revision
commit: af65d7d041d486cc55530e14d806e16143037962
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