On Mon, Oct 26, 2020 at 09:51:08AM -0500, Bjorn Andersson wrote:
On Mon 26 Oct 09:32 CDT 2020, Rob Herring wrote:
quoted
On Tue, Oct 20, 2020 at 09:09:43PM +0530, Manivannan Sadhasivam wrote:
quoted
Add devicetree documentation for 'qcom,freq-domain' property specific
to Qualcomm CPUs. This property is used to reference the CPUFREQ node
along with Domain ID (0/1).
Signed-off-by: Manivannan Sadhasivam <redacted>
---
Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index 1222bf1831fa..f40564bf004f 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -290,6 +290,12 @@ properties:
* arm/msm/qcom,kpss-acc.txt
+ qcom,freq-domain:
+ $ref: '/schemas/types.yaml#/definitions/phandle-array'
+ description: |
+ CPUs supporting freq-domain must set their "qcom,freq-domain" property
+ with phandle to a cpufreq_hw node followed by the Domain ID(0/1).
There's no 3 patches doing the same thing. Mediatek and SCMI are the
others. This will need to be common.
This property is used by existing dtbs for Qualcomm sdm845, sm8150,
sm8250 and sc7180 based devices, so I expect that the support for the
existing property will stay.
Indeed. Any of these can tolerate a change here?
We should still take QCom into account for whatever is come up with for
a common binding.
Rob