On 28.10.22 16:24, Andrew Davis wrote: > Hello all, > > Same story as for AM64x[0], AM62x[1], and J7x[2]. > > Last round for AM65x, but there are some boards that I do not have > (Simatic IOT2050), so testing very welcome! > > Thanks, > Andrew > > [0] https://www.spinics.net/lists/arm-kernel/msg1018532.html > [1] https://www.spinics.net/lists/arm-kernel/msg1018864.html > [2] https://www.spinics.net/lists/arm-kernel/msg1019544.html > > Andrew Davis (11): > arm64: dts: ti: k3-am65: Enable UART nodes at the board level > arm64: dts: ti: k3-am65: Enable I2C nodes at the board level > arm64: dts: ti: k3-am65: Enable SPI nodes at the board level > arm64: dts: ti: k3-am65: Enable EPWM nodes at the board level > arm64: dts: ti: k3-am65: Enable ECAP nodes at the board level > arm64: dts: ti: k3-am65: MDIO pinmux should belong to the MDIO node > arm64: dts: ti: k3-am65: Enable MDIO nodes at the board level > arm64: dts: ti: k3-am65: Enable MCAN nodes at the board level > arm64: dts: ti: k3-am65: Enable PCIe nodes at the board level > arm64: dts: ti: k3-am65: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-am65: Enable McASP nodes at the board level > > .../boot/dts/ti/k3-am65-iot2050-common.dtsi | 101 ++-------------- > arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 41 +++++++ > arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 18 ++- > arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 2 + > .../ti/k3-am6528-iot2050-basic-common.dtsi | 1 + > .../arm64/boot/dts/ti/k3-am654-base-board.dts | 113 ++++-------------- > .../ti/k3-am6548-iot2050-advanced-common.dtsi | 4 - > 7 files changed, 94 insertions(+), 186 deletions(-) > (widely) Tested-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> We are still seeing some likely unrelated issue on our latest board with mainline. Not all aspects could be tested for that reason, but I strongly suspect that this series won't break those. Jan -- Siemens AG, Technology Competence Center Embedded Linux