Re: [PATCH v7 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ Firmware bindings
From: Sudeep Holla <hidden>
Date: 2018-08-08 08:37:50
Also in:
linux-pm, lkml
From: Sudeep Holla <hidden>
Date: 2018-08-08 08:37:50
Also in:
linux-pm, lkml
On Tue, Aug 07, 2018 at 11:15:02PM -0700, Stephen Boyd wrote:
Quoting Taniya Das (2018-08-07 19:46:01)
[...]
quoted
Sudeep, Earlier the design was the freq_domain would take the CPU phandles freq_domain: cpus = <&cpu0 &cpu1....>;I believe Sudeep is recommending something I recommended earlier. It would look like: cpu7 { qcom,freq-domain = <&cpufreq_hw 1>; } to indicate that cpu7 is in cpufreq_hw's frequency domain #1. That should probably be called clk domain BTW.
Thanks Stephen, that's exactly what I meant. You have explained all the details saving me time :)
If that was done with a phandle and a single cell, then we should have something similar on the cpufreq_hw node side indicating how to parse the cells in qcom,freq-domain. A property like #qcom,freq-domain-cells = <1> to indicate that one u32 follows the phandle.
As Saravana mentions in the other email I can't believe it's just made up of logical CPU numbers. If that's the case is it software configurable. -- Regards, Sudeep