From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akashdeep Kaur <a-kaur@ti.com>
Cc: 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, vishalm@ti.com, sebin.francis@ti.com,
k-willis@ti.com
Subject: Re: [PATCH v2 2/6] dt-bindings: opp: ti-cpu: Add ti,soc-info property
Date: Thu, 2 Apr 2026 09:39:18 +0200 [thread overview]
Message-ID: <20260402-sweet-wise-coyote-138ff8@quoll> (raw)
In-Reply-To: <20260401105404.1194717-3-a-kaur@ti.com>
On Wed, Apr 01, 2026 at 04:24:00PM +0530, Akashdeep Kaur wrote:
> 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
Nope, sorry, DT purpose is not to perform probe ordering.
If I change Linux to load k3-socinfo before ti-cpufreq, then the binding
becomes invalid?
Not a DT property, drop.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-02 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 10:53 [PATCH v2 0/6] cpufreq: ti: Fix probe ordering and add device link support for K3 SoCs Akashdeep Kaur
2026-04-01 10:53 ` [PATCH v2 1/6] cpufreq: ti: Add EPROBE_DEFER " Akashdeep Kaur
2026-04-01 10:54 ` [PATCH v2 2/6] dt-bindings: opp: ti-cpu: Add ti,soc-info property Akashdeep Kaur
2026-04-02 7:39 ` Krzysztof Kozlowski [this message]
2026-04-01 10:54 ` [PATCH v2 3/6] cpufreq: ti: Add device link to k3-socinfo Akashdeep Kaur
2026-04-01 10:54 ` [PATCH v2 4/6] arm64: dts: ti: k3-am625: Add ti,soc-info to OPP table Akashdeep Kaur
2026-04-01 10:54 ` [PATCH v2 5/6] arm64: dts: ti: k3-am62a7: " Akashdeep Kaur
2026-04-01 10:54 ` [PATCH v2 6/6] arm64: dts: ti: k3-am62p5: " 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=20260402-sweet-wise-coyote-138ff8@quoll \
--to=krzk@kernel.org \
--cc=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