[0/4] MCSPI clock ID fixes for J7200/J721E/J721S2/J784S4

Message

Anurag Dutta Oct. 23, 2024, 10:45 a.m. UTC

Hi all,
This series fixes the clock IDs for MCSPI instances across:
1) Main and Wakeup domains in j7200
2) Wakeup domain in j721e
3) Main and wakeup domain in j721s2
4) Main domain in j784s4

In j7200, kernel crashes were observed due to incorrect clock IDs.
In j721e/j721s2/j784s4, there was only a mismatch of clock IDs w.r.t
documentation, however it did not trigger a crash. The clock IDs can be
verified from the below links.

Documentation links:
J7200 - https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j7200/clocks.html
J721E - https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/clocks.html
J721S2 - https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721s2/clocks.html
J784S4 - https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j784s4/clocks.html

Test logs:
J7200 EVM CRASH - https://gist.github.com/anuragdutta731/2733fab2d734eea67bd5ad64a2ad982a
J7200 EVM SPI TEST - https://gist.github.com/anuragdutta731/e7f7610a0ff016415d5f58ff314a8c81
J721E EVM SPI TEST - https://gist.github.com/anuragdutta731/d8e63b1298e0c074f6a29544f30c3e87
J721S2 EVM SPI TEST - https://gist.github.com/anuragdutta731/48f6e67f776c025ec98ebe0809dac4a1
J784S4 EVM SPI TEST -https://gist.github.com/anuragdutta731/7c1367c9d0308c5b67a4efa579594970

Anurag Dutta (4):
  arm64: dts: ti: k3-j7200: Fix clock ids for MCSPI instances
  arm64: dts: ti: k3-j721e: Fix clock IDs for MCSPI instances
  arm64: dts: ti: k3-j721s2: Fix clock IDs for MCSPI instances
  arm64: dts: ti: k3-j784s4: Fix clock IDs for MCSPI instances

 arch/arm64/boot/dts/ti/k3-j7200-main.dtsi        | 16 ++++++++--------
 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi  |  6 +++---
 arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi  |  6 +++---
 arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi       | 16 ++++++++--------
 arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi |  6 +++---
 arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi       | 16 ++++++++--------
 6 files changed, 33 insertions(+), 33 deletions(-)

Comments

Vignesh Raghavendra Oct. 30, 2024, 4:54 a.m. UTC | #1

Hi Anurag Dutta,

On Wed, 23 Oct 2024 16:15:28 +0530, Anurag Dutta wrote:
> This series fixes the clock IDs for MCSPI instances across:
> 1) Main and Wakeup domains in j7200
> 2) Wakeup domain in j721e
> 3) Main and wakeup domain in j721s2


> 4) Main domain in j784s4

J784s4 bits dont apply cleanly anymore. Please respin.

> 
> In j7200, kernel crashes were observed due to incorrect clock IDs.
> In j721e/j721s2/j784s4, there was only a mismatch of clock IDs w.r.t
> documentation, however it did not trigger a crash. The clock IDs can be
> verified from the below links.
> 
> [...]

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

[1/4] arm64: dts: ti: k3-j7200: Fix clock ids for MCSPI instances
      commit: 3a47e381670f130870caef6e1155ac531b17b032
[2/4] arm64: dts: ti: k3-j721e: Fix clock IDs for MCSPI instances
      commit: ab09a68f3be04b2f9d1fc7cfc0e2225025cb9421
[3/4] arm64: dts: ti: k3-j721s2: Fix clock IDs for MCSPI instances
      commit: 891874f015e98f67ab2fda76f2e859921e136621

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