Add ti,soc-info property to allow OPP tables to reference the SoC info
device (chipid) for establishing device link dependencies.

This is used on K3 SoCs (AM625, AM62A7, AM62L3, AM62P5) to ensure proper
probe ordering between ti-cpufreq and k3-socinfo drivers. The ti-cpufreq
driver depends on k3-socinfo registering the SoC device for revision
detection via soc_device_match().

The device link also prevents unbinding k3-socinfo while ti-cpufreq is
using it, maintaining system stability.

Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>
---
 .../bindings/opp/operating-points-v2-ti-cpu.yaml      | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml
index 624d1f3f1382..f318494d5295 100644
--- a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml
+++ b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml
@@ -34,6 +34,16 @@ properties:
       points to syscon node representing the control module
       register space of the SoC.
 
+  ti,soc-info:
+    $ref: /schemas/types.yaml#/definitions/phandle
+    description: |
+      Optional phandle to the SoC info device (chipid). Used on K3 SoCs
+      to establish device link dependencies ensuring proper probe ordering
+      (ti-cpufreq after k3-socinfo) and preventing unbinding of k3-socinfo
+      while the OPP table is in use. This is needed because ti-cpufreq uses
+      soc_device_match() to detect SoC revision information provided by
+      k3-socinfo.
+
   opp-shared: true
 
 patternProperties:
@@ -82,6 +92,7 @@ examples:
     opp-table {
         compatible = "operating-points-v2-ti-cpu";
         syscon = <&scm_conf>;
+        ti,soc-info = <&chipid>;
 
         opp-300000000 {
             opp-hz = /bits/ 64 <300000000>;
-- 
2.34.1