From: Akashdeep Kaur <a-kaur@ti.com>
To: <praneeth@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <d-gole@ti.com>
Cc: <vishalm@ti.com>, <sebin.francis@ti.com>, <k-willis@ti.com>,
<a-kaur@ti.com>
Subject: [PATCH 3/5] arm64: dts: ti: k3-am62a7: Add ti,soc-info to OPP table
Date: Mon, 30 Mar 2026 17:31:03 +0530 [thread overview]
Message-ID: <20260330120105.2985200-4-a-kaur@ti.com> (raw)
In-Reply-To: <20260330120105.2985200-1-a-kaur@ti.com>
Link CPU OPP table to k3-socinfo driver for dependency tracking.
Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62a7.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62a7.dtsi b/arch/arm64/boot/dts/ti/k3-am62a7.dtsi
index b6e5eee99370..6d1459e9ea71 100644
--- a/arch/arm64/boot/dts/ti/k3-am62a7.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62a7.dtsi
@@ -109,6 +109,7 @@ a53_opp_table: opp-table {
compatible = "operating-points-v2-ti-cpu";
opp-shared;
syscon = <&opp_efuse_table>;
+ ti,soc-info = <&chipid>;
opp-200000000 {
opp-hz = /bits/ 64 <200000000>;
--
2.34.1
next prev parent reply other threads:[~2026-03-30 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 12:01 [PATCH 0/5] cpufreq: ti: Fix probe ordering and add device link support for K3 SoCs Akashdeep Kaur
2026-03-30 12:01 ` [PATCH 1/5] cpufreq: ti: Add EPROBE_DEFER " Akashdeep Kaur
2026-03-30 12:01 ` [PATCH 2/5] arm64: dts: ti: k3-am625: Add ti,soc-info to OPP table Akashdeep Kaur
2026-03-30 12:01 ` Akashdeep Kaur [this message]
2026-03-30 12:01 ` [PATCH 4/5] arm64: dts: ti: k3-am62p5: " Akashdeep Kaur
2026-03-30 12:01 ` [PATCH 5/5] cpufreq: ti: Add device link to k3-socinfo Akashdeep Kaur
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=20260330120105.2985200-4-a-kaur@ti.com \
--to=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@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=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sebin.francis@ti.com \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
--cc=vishalm@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