Hi Bhavya Kapoor,
On Wed, 14 Feb 2024 16:28:42 +0530, Bhavya Kapoor wrote:
> WKUP_PADCONFIG registers for wkup_uart0 and mcu_uart0 lies under
> wkup_pmx2 for J7200. Thus, modify pinmux for both of them. Also,
> remove the redundant clock-frequency property from mcu_uart0 node.
>
> Only Tx and Rx Signal lines for wkup_uart0 are brought out on
> J721S2 Common Proc Board and J784S4 EVM, but CTS and RTS signal lines
> are not brought out. Thus, remove pinmux for CTS and RTS signal lines
> for wkup_uart0 in J721S2 and J784S4.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/4] arm64: dts: ti: k3-j7200-common-proc-board: Modify Pinmux for wkup_uart0 and mcu_uart0
commit: 566feddd2ba5e29d9ccab36d6508592ae563f275
[2/4] arm64: dts: ti: k3-j7200-common-proc-board: Remove clock-frequency from mcu_uart0
commit: 0fa8b0e2083d333e4854b9767fb893f924e70ae5
[3/4] arm64: dts: ti: k3-j721s2-common-proc-board: Remove Pinmux for CTS and RTS in wkup_uart0
commit: 28e5b74d524050008edf415f20a3e38907b8f176
[4/4] arm64: dts: ti: k3-j784s4-evm: Remove Pinmux for CTS and RTS in wkup_uart0
commit: d29a6cf980572d8cf7b63935716fca663e2610f0
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
