mbox series

[00/11] AM65x Disable Incomplete DT Nodes

Message ID 20221028142417.10642-1-afd@ti.com
Headers
Series AM65x Disable Incomplete DT Nodes |

Message

Andrew Davis Oct. 28, 2022, 2:24 p.m. UTC 
  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(-)

Comments

Bryan Brattlof Oct. 31, 2022, 2:54 p.m. UTC | #1 
On October 28, 2022 thus sayeth Andrew Davis:
> 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

LGTM! Thanks Andrew!

Reviewed-by: Bryan Brattlof <bb@ti.com>

~Bryan
Jan Kiszka Nov. 3, 2022, 1:20 p.m. UTC | #2 
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@siemens.com>

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
Nishanth Menon Nov. 4, 2022, 2:57 a.m. UTC | #3 
Hi Andrew Davis,

On Fri, 28 Oct 2022 09:24:06 -0500, Andrew Davis wrote:
> 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
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[01/11] arm64: dts: ti: k3-am65: Enable UART nodes at the board level
        commit: 65e8781ac90e74242ebb1a98bf415809e8387aaf
[02/11] arm64: dts: ti: k3-am65: Enable I2C nodes at the board level
        commit: c0a5ba87af56f073145dd026280454aec4a44db0
[03/11] arm64: dts: ti: k3-am65: Enable SPI nodes at the board level
        commit: 1c49cbb19b1f2c61168741f987e65b50dd2f97de
[04/11] arm64: dts: ti: k3-am65: Enable EPWM nodes at the board level
        commit: 5780cf09409551c67112127b90786e553c8f9a25
[05/11] arm64: dts: ti: k3-am65: Enable ECAP nodes at the board level
        commit: c1d1189eafb27fa5c0cb0b92a4e81c155709068b
[06/11] arm64: dts: ti: k3-am65: MDIO pinmux should belong to the MDIO node
        commit: 0edd6d7ed646a53b41d09f7aa1d8c01d23bd7b73
[07/11] arm64: dts: ti: k3-am65: Enable MDIO nodes at the board level
        commit: c75c5c0bba500b1e454dc2591acdd6596fe64ce2
[08/11] arm64: dts: ti: k3-am65: Enable MCAN nodes at the board level
        commit: b08bf4a5c0ed0a6b8472ca78ccf416d73d2609aa
[09/11] arm64: dts: ti: k3-am65: Enable PCIe nodes at the board level
        commit: 7ff8432c272e3556461b7c9daad8156ae446e812
[10/11] arm64: dts: ti: k3-am65: Enable Mailbox nodes at the board level
        commit: 3f9089ea008c195b6cf449735c5a3a5fcac1a382
[11/11] arm64: dts: ti: k3-am65: Enable McASP nodes at the board level
        commit: fdb02688f22b397c811328bf826b5b110d5cdc41

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