On 30/09/13 09:52, Mark Rutland wrote:
> Hi Sudeep,
>
> I have a few comments.
>
> On Wed, Sep 18, 2013 at 11:58:11AM +0100, Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@xxxxxxx>
>>
>> If more than one similar devices share the same operating points(OPPs)
>> being in the same clock domain, currently we need to replicate the
>> OPP entries in all the nodes.
>>
>> This patch extends existing binding by adding a new property named
>> 'operating-points-phandle' to specify the phandle in any device node
>> pointing to another node which contains the actual OPP tuples.
>> This helps to avoid replication if multiple devices share the OPPs.
>>
>> Cc: Rob Herring <rob.herring@xxxxxxxxxxx>
>> Cc: Pawel Moll <pawel.moll@xxxxxxx>
>> Cc: Mark Rutland <mark.rutland@xxxxxxx>
>> Cc: Kumar Gala <galak@xxxxxxxxxxxxxx>
>> Cc: Stephen Warren <swarren@xxxxxxxxxxxxx>
>> Cc: "Rafael J. Wysocki" <rjw@xxxxxxx>
>> Cc: Nishanth Menon <nm@xxxxxx>
>> Signed-off-by: Sudeep KarkadaNagesha <sudeep.karkadanagesha@xxxxxxx>
>> ---
>> Documentation/devicetree/bindings/power/opp.txt | 152 ++++++++++++++++++++++--
>> 1 file changed, 140 insertions(+), 12 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt
>> index 74499e5..e9fea65 100644
>> --- a/Documentation/devicetree/bindings/power/opp.txt
>> +++ b/Documentation/devicetree/bindings/power/opp.txt
>> @@ -4,22 +4,150 @@ SoCs have a standard set of tuples consisting of frequency and
>> voltage pairs that the device will support per voltage domain. These
>> are called Operating Performance Points or OPPs.
>>
>> -Properties:
>> +Required Properties:
>> - operating-points: An array of 2-tuples items, and each item consists
>> of frequency and voltage like <freq-kHz vol-uV>.
>> freq: clock frequency in kHz
>> vol: voltage in microvolt
>>
>> +Optional properties:
>> +- operating-points-phandle: phandle to the device tree node which contains
>> + the operating points tuples(recommended to be used if multiple
>> + devices are in the same clock domain and hence share OPPs, as it
>> + avoids replication of OPPs)
>> +
>
> I assume if you have an operating-points-phandle property,
> operating-points it no longer required. That should probably be
> described.
>
Correct, infact do it make sense to list both operating-points and
operating-points-phandle as required property but they are mutually exclusive ?
>> Examples:
>>
>> -cpu@0 {
>> - compatible = "arm,cortex-a9";
>> - reg = <0>;
>> - next-level-cache = <&L2>;
>> - operating-points = <
>> - /* kHz uV */
>> - 792000 1100000
>> - 396000 950000
>> - 198000 850000
>> - >;
>> -};
>> +1. A uniprocessor system (phandle not required)
>> +
>> + cpu0: cpu@0 {
>> + compatible = "arm,cortex-a9";
>> + reg = <0>;
>> + operating-points = <
>> + /* kHz uV */
>> + 792000 1100000
>> + 396000 950000
>> + 198000 850000
>> + >;
>> + };
>> +
>> +If more than one device of same type share the same OPPs, for example
>> +all the CPUs on a SoC or in a single cluster on a SoC, then we need to
>> +avoid replicating the OPPs in all the nodes. We can specify the phandle
>> +of the node which contains the OPP tuples
>
> This seems a bit out of place given the example immediately below.
>
Sorry carried from previous version, will fix it.
>> +
>> +2a. Consider a SMP system with 4 CPUs in the same clock domain
>> + (backward compatible style, only CPU0 contains OPP)
>> +
>> + cpu0: cpu@0 {
>> + compatible = "arm,cortex-a9";
>> + reg = <0>;
>> + operating-points = <
>> + /* kHz uV */
>> + 792000 1100000
>> + 396000 950000
>> + 198000 850000
>> + >;
>> + };
>> +
>> + cpu1: cpu@1 {
>> + compatible = "arm,cortex-a9";
>> + reg = <1>;
>> + };
>> +
>> + cpu2: cpu@2 {
>> + compatible = "arm,cortex-a9";
>> + reg = <2>;
>> + };
>> +
>> + cpu3: cpu@3 {
>> + compatible = "arm,cortex-a9";
>> + reg = <3>;
>> + };
>
> This "backward compatible style" doesn't seem to actually be described
> anywhere, and the paragraph above about phandles makes it somewhat
> confusing.
>
Not sure if this is needed at all here. I must say there's nothing called
backward compatible style, the only reason I added it to tell that existing
cpufreq-cpu0 DTs continue to work.
I would say it's more like some agreement with the existing binding and the
cpufreq-cpu0 driver. Do it make sense to drop it from here ?
>> +
>> +2b. Consider a SMP system with 4 CPUs in the same clock domain
>> + (using operating-points-phandle)
>> +
>> + cpu0: cpu@0 {
>> + compatible = "arm,cortex-a9";
>> + reg = <0>;
>> + operating-points-phandle = <&cpu_opp>;
>> + };
>> +
>> + cpu1: cpu@1 {
>> + compatible = "arm,cortex-a9";
>> + reg = <1>;
>> + operating-points-phandle = <&cpu_opp>;
>> + };
>> +
>> + cpu2: cpu@2 {
>> + compatible = "arm,cortex-a9";
>> + reg = <2>;
>> + operating-points-phandle = <&cpu_opp>;
>> + };
>> +
>> + cpu3: cpu@3 {
>> + compatible = "arm,cortex-a9";
>> + reg = <3>;
>> + operating-points-phandle = <&cpu_opp>;
>> + };
>> +
>> + operating_points {
>> + cpu_opp: cpu_opp {
>> + operating-points = <
>> + /* kHz uV */
>> + 792000 1100000
>> + 396000 950000
>> + 198000 850000
>> + >;
>> + };
>> + ... /* other device OPP nodes */
>> + }
>
> Is this all inside the /cpus node?
>
It can be anywhere, if only cpus share OPPs on a system, it can be placed under
/cpus. The idea to put all OPP nodes under one node is just for readibility
purposes. As along as phandle is correct it doesn't matter where the exact nodes
are. Does this need to be mentioned explicity in the binding ?
> Is the "operating_points" name important?
>
> Are all OPP tables expected to be in the same "operating_points" node?
>
No for both the above questions, again just for readibilty I chose that name and
placed all OPP nodes under same node in the example, it can be named anything
and can be scattered.
Again does this need to be mentioned explicity in the binding ?
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
