| Message ID | 20221018211533.21335-1-afd@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | AM62x Disable Incomplete DT Nodes | expand |
On October 18, 2022 thus sayeth Andrew Davis: > Hello all, > > Same story as for AM64x[0], this time for AM62x. If there > are no objections here then the J7x platforms are next. > > Thanks, > Andrew > > [0] https://www.spinics.net/lists/arm-kernel/msg1018532.html Not a lore fan is see ;) > > Andrew Davis (10): > arm64: dts: ti: k3-am62: Enable UART nodes at the board level > arm64: dts: ti: k3-am62: Enable I2C nodes at the board level > arm64: dts: ti: k3-am62: Enable SPI nodes at the board level > arm64: dts: ti: k3-am62: Enable EPWM nodes at the board level > arm64: dts: ti: k3-am62: Enable ECAP nodes at the board level > arm64: dts: ti: k3-am62: MDIO pinmux should belong to the MDIO node > arm64: dts: ti: k3-am62: Enable MDIO nodes at the board level > arm64: dts: ti: k3-am62: Enable MCAN nodes at the board level > arm64: dts: ti: k3-am62: Enable SDHCI nodes at the board level > arm64: dts: ti: k3-am62: Enable OSPI nodes at the board level > > arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 26 +++++++ > arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 4 ++ > arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 2 + > arch/arm64/boot/dts/ti/k3-am625-sk.dts | 81 +++------------------- > 4 files changed, 43 insertions(+), 70 deletions(-) > LGTM! Reviewed-by: Bryan Brattlof <bb@ti.com> ~Bryan
On 19/10/22 2:45 am, Andrew Davis wrote: > > Andrew Davis (10): > arm64: dts: ti: k3-am62: Enable UART nodes at the board level > arm64: dts: ti: k3-am62: Enable I2C nodes at the board level > arm64: dts: ti: k3-am62: Enable SPI nodes at the board level > arm64: dts: ti: k3-am62: Enable EPWM nodes at the board level > arm64: dts: ti: k3-am62: Enable ECAP nodes at the board level > arm64: dts: ti: k3-am62: MDIO pinmux should belong to the MDIO node > arm64: dts: ti: k3-am62: Enable MDIO nodes at the board level > arm64: dts: ti: k3-am62: Enable MCAN nodes at the board level > arm64: dts: ti: k3-am62: Enable SDHCI nodes at the board level > arm64: dts: ti: k3-am62: Enable OSPI nodes at the board level > > arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 26 +++++++ > arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 4 ++ > arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 2 + > arch/arm64/boot/dts/ti/k3-am625-sk.dts | 81 +++------------------- > 4 files changed, 43 insertions(+), 70 deletions(-) > Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
Hi Andrew Davis, On Tue, 18 Oct 2022 16:15:23 -0500, Andrew Davis wrote: > Same story as for AM64x[0], this time for AM62x. If there > are no objections here then the J7x platforms are next. > > Thanks, > Andrew > > [0] https://www.spinics.net/lists/arm-kernel/msg1018532.html > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [01/10] arm64: dts: ti: k3-am62: Enable UART nodes at the board level commit: b5877d9b409cfd5667813e667cbc27192a0fb9ea [02/10] arm64: dts: ti: k3-am62: Enable I2C nodes at the board level commit: a1541a08bbf9d02f842801261d0dd4505bcd29e0 [03/10] arm64: dts: ti: k3-am62: Enable SPI nodes at the board level commit: 361e8b7144405b78bd37cc3e9b2d23fc2e2ed6d5 [04/10] arm64: dts: ti: k3-am62: Enable EPWM nodes at the board level commit: 6e5474826606a783dd969467f93b0c6a56c39780 [05/10] arm64: dts: ti: k3-am62: Enable ECAP nodes at the board level commit: ffd61c16fe8facf56b6fb06e29ba5bd150f01bd9 [06/10] arm64: dts: ti: k3-am62: MDIO pinmux should belong to the MDIO node commit: 8709e0442c79c03f7067d6e7464d669504f76527 [07/10] arm64: dts: ti: k3-am62: Enable MDIO nodes at the board level commit: 1f737012ce7bd92aecf7d6b1e17742dc7cae7bee [08/10] arm64: dts: ti: k3-am62: Enable MCAN nodes at the board level commit: 2f6d7e18e73d3bd3752ca16d0b3c6b2926809452 [09/10] arm64: dts: ti: k3-am62: Enable SDHCI nodes at the board level commit: b2b10301ca685ac23f09d2e663eb4b990b871935 [10/10] arm64: dts: ti: k3-am62: Enable OSPI nodes at the board level commit: b0ca32e895680ba94c0ef24a5faa738e536e31cc 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] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git