Hi Jai Luthra,
On Thu, 06 Jun 2024 13:37:39 +0530, Jai Luthra wrote:
> Drop McASP AFIFOs for all AM62 based platforms, as the extra buffering
> is not needed with BCDMA already having internal buffering.
>
> Also fix the pinmux for McASP1 on AM62P.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/7] arm64: dts: ti: k3-am62x: Drop McASP AFIFOs
commit: 6ee3ca0ec7fabc63603afdb3485da04164dc8747
[2/7] arm64: dts: ti: k3-am62a7: Drop McASP AFIFOs
commit: a931b81072921a11d5bb8e8201b6228b791d40a9
[3/7] arm64: dts: ti: k3-am62p5: Drop McASP AFIFOs
commit: d3fe4b4e2e44de64ed1f1585151bf4a3627adbaf
[4/7] arm64: dts: ti: k3-am625-beagleplay: Drop McASP AFIFOs
commit: 3b4a03357aee07a32a44a49bb6a71f5e82b1ecc1
[5/7] arm64: dts: ti: k3-am62-verdin: Drop McASP AFIFOs
commit: fb01352801f08740e9f37cbd71f73866c7044927
[6/7] arm64: dts: ti: k3-am625-phyboard-lyra-rdk: Drop McASP AFIFOs
commit: 554dd562a5f2f5d7e838f7b229a1c612275678db
[7/7] arm64: dts: ti: k3-am62p5-sk: Fix pinmux for McASP1 TX
commit: e96e36ce1fdcf08a70e3f09cbe2da02b073c58ac
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh
