From: Anurag Dutta <a-dutta@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<vaishnav.a@ti.com>, <j-keerthy@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>
Subject: [PATCH 0/4] MCSPI clock ID fixes for J7200/J721E/J721S2/J784S4
Date: Wed, 23 Oct 2024 16:15:28 +0530 [thread overview]
Message-ID: <20241023104532.3438851-1-a-dutta@ti.com> (raw)
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(-)
--
2.34.1
next reply other threads:[~2024-10-23 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 10:45 Anurag Dutta [this message]
2024-10-23 10:45 ` [PATCH 1/4] arm64: dts: ti: k3-j7200: Fix clock ids for MCSPI instances Anurag Dutta
2024-10-24 6:22 ` Aniket Limaye
2024-10-23 10:45 ` [PATCH 2/4] arm64: dts: ti: k3-j721e: Fix clock IDs " Anurag Dutta
2024-10-23 10:45 ` [PATCH 3/4] arm64: dts: ti: k3-j721s2: " Anurag Dutta
2024-10-23 10:45 ` [PATCH 4/4] arm64: dts: ti: k3-j784s4: " Anurag Dutta
2024-10-30 4:54 ` (subset) [PATCH 0/4] MCSPI clock ID fixes for J7200/J721E/J721S2/J784S4 Vignesh Raghavendra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241023104532.3438851-1-a-dutta@ti.com \
--to=a-dutta@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®