PM / OPP v2 & cpufreq backports part 1
Subsystems (7)
v3 cover PM / OPP v2 & cpufreq backports part 1
Hi everyone,
This is v3 of the part 1 of MOXA's PM / OPP / cpufreq backport series. Changes since v2:
- Squashed "PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties" into "PM / OPP: Parse 'opp-<prop>-<name>' bindings"
Changes since v1:
- Added missing SoB and upstream commit hash for "PM / OPP: Set
cpu_dev->id in cpumask first"
Original cover letter:
This is part 1 of MOXA's PM / OPP / cpufreq backport series. The whole series aims to backport patches related to PM / OPPv2 and cpufreq which were included in the v4.4 kernel from TI's SDK. The end goal is to include cpufreq-ti and convert am33xx to using it and OPPv2.
Part 1 here includes patches from the v4.5 cycle, listed in topological order:
deaa51465105 PM / OPP: Add debugfs support
1c4d12de2719 PM / OPP: Add "opp-supported-hw" binding
ffdb8cc7a27c PM / OPP: Add {opp-microvolt|opp-microamp}-<name> binding af87a39a5f7c PM / OPP: Remove 'operating-points-names' binding 754dcf35f346 PM / OPP: Rename OPP nodes as opp@<opp-hz>
dc4e7b1fa20a PM / OPP: Add missing doc comments
7de36b0aa51a PM / OPP: Parse 'opp-supported-hw' binding
01fb4d3c39d3 PM / OPP: Parse 'opp-<prop>-<name>' bindings fd8d8e63467c PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties d9de19b1cc01 PM / OPP: Set cpu_dev->id in cpumask first
5ff24d601092 PM / OPP: Use snprintf() instead of sprintf() 3be3f8f36e73 devicetree: bindings: Add optional dynamic-power-coefficient property f8fa8ae06b8c cpufreq-dt: Supply power coefficient when registering cooling devices 929ca89c305a cpufreq-dt: fix handling regulator_get_voltage() result b331bc20d928 cpufreq: cpufreq-dt: avoid uninitialized variable warnings:
Of these,
dc4e7b1fa20a PM / OPP: Add missing doc comments
was identified as a patch dependency, but otherwise serves no purpose. And
d9de19b1cc01 PM / OPP: Set cpu_dev->id in cpumask first
was found while looking through git logs. Last,
3be3f8f36e73 devicetree: bindings: Add optional dynamic-power-coefficient property
is related to
f8fa8ae06b8c cpufreq-dt: Supply power coefficient when registering cooling devices
All other patches were included from TI's SDK.
The patches apply cleanly on top of linux-4.4.y-cip. Please have a look.
Regards
ChenYu
Andrzej Hajda (1):
cpufreq-dt: fix handling regulator_get_voltage() result
Arnd Bergmann (1):
cpufreq: cpufreq-dt: avoid uninitialized variable warnings:
Pi-Cheng Chen (1):
PM / OPP: Set cpu_dev->id in cpumask first
Punit Agrawal (2):
devicetree: bindings: Add optional dynamic-power-coefficient property
cpufreq-dt: Supply power coefficient when registering cooling devices
Viresh Kumar (9):
PM / OPP: Add debugfs support
PM / OPP: Add "opp-supported-hw" binding
PM / OPP: Add {opp-microvolt|opp-microamp}-<name> binding PM / OPP: Remove 'operating-points-names' binding PM / OPP: Rename OPP nodes as opp@<opp-hz>
PM / OPP: Add missing doc comments
PM / OPP: Parse 'opp-supported-hw' binding
PM / OPP: Parse 'opp-<prop>-<name>' bindings
PM / OPP: Use snprintf() instead of sprintf()
.../devicetree/bindings/arm/cpus.txt | 17 + Documentation/devicetree/bindings/opp/opp.txt | 132 +++++-- drivers/base/power/opp/Makefile | 1 + drivers/base/power/opp/core.c | 336 +++++++++++++++++- drivers/base/power/opp/cpu.c | 3 +- drivers/base/power/opp/debugfs.c | 219 ++++++++++++ drivers/base/power/opp/opp.h | 53 ++- drivers/cpufreq/cpufreq-dt.c | 29 +- include/linux/pm_opp.h | 22 ++ 9 files changed, 742 insertions(+), 70 deletions(-) create mode 100644 drivers/base/power/opp/debugfs.c
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4773): https://lists.cip-project.org/g/cip-dev/message/4773
Mute This Topic: https://lists.cip-project.org/mt/74768055/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 1/14 PM / OPP: Add debugfs support
From: Viresh Kumar <[email protected]>
commit deaa51465105a7eda19a627b10372f4f7c51a4df upstream.
This patch adds debugfs support to OPP layer to export OPPs and their properties for all the devices.
This creates a top level directory: /sys/kernel/debug/opp and then device specific directories (based on device names) inside it. For
example: 'cpu0', 'cpu1', etc..
If multiple devices share the OPP table, then the real directory is created only for the first device. For all others, links are created to the real directory.
Inside the device specific directory, a separate directory is created for each OPP. And within that files per opp property.
--- drivers/base/power/opp/Makefile | 1 + drivers/base/power/opp/core.c | 21 ++- drivers/base/power/opp/debugfs.c | 219 +++++++++++++++++++++++++++++++ drivers/base/power/opp/opp.h | 42 ++++++ 4 files changed, 281 insertions(+), 2 deletions(-) create mode 100644 drivers/base/power/opp/debugfs.c
drivers/base/power/opp/Makefile +1 -0
@@ -1,2 +1,3 @@ ccflags-$(CONFIG_DEBUG_DRIVER) := -DDEBUG obj-y += core.o cpu.o +obj-$(CONFIG_DEBUG_FS) += debugfs.o
drivers/base/power/opp/core.c +19 -2
@@ -463,6 +463,7 @@ static void _kfree_list_dev_rcu(struct rcu_head *head)static void _remove_list_dev (struct device_list_opp *list_dev,struct device_opp *dev_opp) { +opp_debug_unregister (list_dev, dev_opp);list_del (&list_dev->node);call_srcu (&dev_opp->srcu_head.srcu, &list_dev->rcu_head, _kfree_list_dev_rcu);
@@ -472,6 +473,7 @@ struct device_list_opp *_add_list_dev(const struct device *dev, struct device_opp *dev_opp) {struct device_list_opp *list_dev; +int ret; list_dev =kzalloc (sizeof (*list_dev),GFP_KERNEL );if (!list_dev)
@@ -481,6 +483,12 @@ struct device_list_opp *_add_list_dev(const struct device *dev, list_dev->dev = dev;list_add_rcu (&list_dev->node, &dev_opp->dev_list); +/* Create debugfs entries for the dev_opp */ + ret =opp_debug_register (list_dev, dev_opp); +if (ret) +dev_err (dev,"%s: Failed to register opp debugfs (%d)\n" , + __func__, ret); +return list_dev; }
@@ -596,6 +604,7 @@ static void _opp_remove(struct device_opp *dev_opp,*/ if (notify)srcu_notifier_call_chain (&dev_opp->srcu_head,OPP_EVENT_REMOVE , opp); +opp_debug_remove_one (opp);list_del_rcu (&opp->node);call_srcu (&dev_opp->srcu_head.srcu, &opp->rcu_head, _kfree_opp_rcu);
@@ -673,6 +682,7 @@ static int _opp_add(struct device *dev, struct dev_pm_opp *new_opp, {struct dev_pm_opp *opp;struct list_head *head = &dev_opp->opp_list; +int ret;/* * Insert new OPP in order of increasing frequency and discard if
@@ -703,6 +713,11 @@ static int _opp_add(struct device *dev, struct dev_pm_opp *new_opp, new_opp->dev_opp = dev_opp;list_add_rcu (&new_opp->node, head); + ret =opp_debug_create_one (new_opp, dev_opp); +if (ret) +dev_err (dev,"%s: Failed to register opp to debugfs (%d)\n" , + __func__, ret); +return 0 ; }
@@ -895,12 +910,14 @@ static int _opp_add_static_v2(struct device *dev, struct device_node *np)/* OPP to select on device suspend */ if (of_property_read_bool (np,"opp-suspend" )) { -if (dev_opp->suspend_opp) +if (dev_opp->suspend_opp) {dev_warn (dev,"%s: Multiple suspend OPPs found (%lu %lu)\n" , __func__, dev_opp->suspend_opp->rate, new_opp->rate); -else + }else { + new_opp->suspend = true; dev_opp->suspend_opp = new_opp; + } }if (new_opp->clock_latency_ns > dev_opp->clock_latency_ns_max)
drivers/base/power/opp/debugfs.c new file +219 -0
219 lines not on this page · raw message
drivers/base/power/opp/opp.h +42 -0
100 lines not on this page · raw message
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4775): https://lists.cip-project.org/g/cip-dev/message/4775
Mute This Topic: https://lists.cip-project.org/mt/74768061/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 2/14 PM / OPP: Add "opp-supported-hw" binding
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit 1c4d12de2719dfdf27c6dab31e7a5641ee293c94 upstream.
We may want to enable only a subset of OPPs, from the bigger list of OPPs, based on what version of the hardware we are running on. This would enable us to not duplicate OPP tables for every version of the hardware we support.
To enable that, this patch defines a new property 'opp-supported-hw'. It can support any number of hierarchy levels of the versions the hardware follows. And based on the selected hardware versions, we can pick only the relevant OPPs at runtime.
--- Documentation/devicetree/bindings/opp/opp.txt | 65 +++++++++++++++++++ 1 file changed, 65 insertions(+)
Documentation/devicetree/bindings/opp/opp.txt +65 -0
@@ -123,6 +123,26 @@ Optional properties: - opp-suspend: Marks the OPP to be used during device suspend. Only one OPP in the table should have this. +- opp-supported-hw: This enables us to select only a subset of OPPs from the + larger OPP table, based on what version of the hardware we are running on. We + still can't have multiple nodes with the same opp-hz value in OPP table. + + It's an user defined array containing a hierarchy of hardware version numbers, + supported by the OPP. For example: a platform with hierarchy of three levels + of versions (A, B and C), this field should be like <X Y Z>, where X + corresponds to Version hierarchy A, Y corresponds to version hierarchy B and Z + corresponds to version hierarchy C. + + Each level of hierarchy is represented by a 32 bit value, and so there can be + only 32 different supported version per hierarchy. i.e. 1 bit per version. A + value of 0xFFFFFFFF will enable the OPP for all versions for that hierarchy + level. And a value of 0x00000000 will disable the OPP completely, and so we + never want that to happen. + + If 32 values aren't sufficient for a version hierarchy, than that version + hierarchy can be contained in multiple 32 bit values. i.e. <X Y Z1 Z2> in the + above example, Z1 & Z2 refer to the version hierarchy Z. + - status: Marks the node enabled/disabled. Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
@@ -463,3 +483,48 @@ Example 5: Multiple OPP tables }; }; }; + +Example 6: opp-supported-hw +(example: three level hierarchy of versions: cuts, substrate and process) + +/ { + cpus { + cpu@0 { + compatible = "arm,cortex-a7"; + ... + + cpu-supply = <&cpu_supply> + operating-points-v2 = <&cpu0_opp_table_slow>; + }; + }; + + opp_table { + compatible = "operating-points-v2"; + status = "okay"; + opp-shared; + + opp00 { + /* + * Supports all substrate and process versions for 0xF + * cuts, i.e. only first four cuts. + */ + opp-supported-hw = <0xF 0xFFFFFFFF 0xFFFFFFFF> + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <900000 915000 925000>; + ... + }; + + opp01 { + /* + * Supports: + * - cuts: only one, 6th cut (represented by 6th bit). + * - substrate: supports 16 different substrate versions + * - process: supports 9 different process versions + */ + opp-supported-hw = <0x20 0xff0000ff 0x0000f4f0> + opp-hz = /bits/ 64 <800000000>; + opp-microvolt = <900000 915000 925000>; + ... + }; + }; +};
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4777): https://lists.cip-project.org/g/cip-dev/message/4777
Mute This Topic: https://lists.cip-project.org/mt/74768063/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 3/14 PM / OPP: Add {opp-microvolt|opp-microamp}-<name> binding
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit ffdb8cc7a27c89175e541e68e2a73f1f63ab8c6b upstream.
Depending on the version of hardware or its properties, which are only known at runtime, various properties of the OPP can change. For example, an OPP with frequency 1.2 GHz, may have different voltage/current requirements based on the version of the hardware it is running on.
In order to not replicate the same OPP tables for varying values of all such fields, this commit introduces the concept of opp-property-<name>. The <name> can be chosen by the platform at runtime, and OPPs will be initialized depending on that name string. Currently support is extended for the following properties:
- opp-microvolt-<name>
- opp-microamp-<name>
If the name string isn't provided by the platform, or if it is provided but doesn't match the properties present in the OPP node, we will fall back to the original properties without the -<name> string, if they are available.
--- Documentation/devicetree/bindings/opp/opp.txt | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+)
Documentation/devicetree/bindings/opp/opp.txt +47 -0
@@ -100,6 +100,14 @@ Optional properties: Entries for multiple regulators must be present in the same order as regulators are specified in device's DT node. +- opp-microvolt-<name>: Named opp-microvolt property. This is exactly similar to + the above opp-microvolt property, but allows multiple voltage ranges to be + provided for the same OPP. At runtime, the platform can pick a <name> and + matching opp-microvolt-<name> property will be enabled for all OPPs. If the + platform doesn't pick a specific <name> or the <name> doesn't match with any + opp-microvolt-<name> properties, then opp-microvolt property shall be used, if + present. + - opp-microamp: The maximum current drawn by the device in microamperes considering system specific parameters (such as transients, process, aging, maximum operating temperature range etc.) as necessary. This may be used to
@@ -112,6 +120,9 @@ Optional properties: for few regulators, then this should be marked as zero for them. If it isn't required for any regulator, then this property need not be present. +- opp-microamp-<name>: Named opp-microamp property. Similar to + opp-microvolt-<name> property, but for microamp instead. + - clock-latency-ns: Specifies the maximum possible transition latency (in nanoseconds) for switching to this OPP from any other OPP.
@@ -528,3 +539,39 @@ Example 6: opp-supported-hw }; }; }; + +Example 7: opp-microvolt-<name>, opp-microamp-<name>: +(example: device with two possible microvolt ranges: slow and fast) + +/ { + cpus { + cpu@0 { + compatible = "arm,cortex-a7"; + ... + + operating-points-v2 = <&cpu0_opp_table>; + }; + }; + + cpu0_opp_table: opp_table0 { + compatible = "operating-points-v2"; + opp-shared; + + opp00 { + opp-hz = /bits/ 64 <1000000000>; + opp-microvolt-slow = <900000 915000 925000>; + opp-microvolt-fast = <970000 975000 985000>; + opp-microamp-slow = <70000>; + opp-microamp-fast = <71000>; + }; + + opp01 { + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt-slow = <900000 915000 925000>, /* Supply vcc0 */ + <910000 925000 935000>; /* Supply vcc1 */ + opp-microvolt-fast = <970000 975000 985000>, /* Supply vcc0 */ + <960000 965000 975000>; /* Supply vcc1 */ + opp-microamp = <70000>; /* Will be used for both slow/fast */ + }; + }; +};
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4774): https://lists.cip-project.org/g/cip-dev/message/4774
Mute This Topic: https://lists.cip-project.org/mt/74768060/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 4/14 PM / OPP: Remove 'operating-points-names' binding
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit af87a39a5f7cf6ef252b1aec3e2e6508a40e51f1 upstream.
These aren't used until now by any DT files and wouldn't be used now as we have a better scheme in place now, i.e. opp-property-<name> properties.
Remove the (useless) binding without breaking ABI.
--- Documentation/devicetree/bindings/opp/opp.txt | 62 +------------------ 1 file changed, 2 insertions(+), 60 deletions(-)
Documentation/devicetree/bindings/opp/opp.txt +2 -60
@@ -45,21 +45,10 @@ Devices supporting OPPs must set their "operating-points-v2" property with phandle to a OPP table in their DT node. The OPP core will use this phandle to find the operating points for the device. -Devices may want to choose OPP tables at runtime and so can provide a list of -phandles here. But only *one* of them should be chosen at runtime. This must be -accompanied by a corresponding "operating-points-names" property, to uniquely -identify the OPP tables. - If required, this can be extended for SoC vendor specfic bindings. Such bindings should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt and should have a compatible description like: "operating-points-v2-<vendor>". -Optional properties: -- operating-points-names: Names of OPP tables (required if multiple OPP - tables are present), to uniquely identify them. The same list must be present - for all the CPUs which are sharing clock/voltage rails and hence the OPP - tables. - * OPP Table Node This describes the OPPs belonging to a device. This node can have following
@@ -448,54 +437,7 @@ Example 4: Handling multiple regulators }; }; -Example 5: Multiple OPP tables - -/ { - cpus { - cpu@0 { - compatible = "arm,cortex-a7"; - ... - - cpu-supply = <&cpu_supply> - operating-points-v2 = <&cpu0_opp_table_slow>, <&cpu0_opp_table_fast>; - operating-points-names = "slow", "fast"; - }; - }; - - cpu0_opp_table_slow: opp_table_slow { - compatible = "operating-points-v2"; - status = "okay"; - opp-shared; - - opp00 { - opp-hz = /bits/ 64 <600000000>; - ... - }; - - opp01 { - opp-hz = /bits/ 64 <800000000>; - ... - }; - }; - - cpu0_opp_table_fast: opp_table_fast { - compatible = "operating-points-v2"; - status = "okay"; - opp-shared; - - opp10 { - opp-hz = /bits/ 64 <1000000000>; - ... - }; - - opp11 { - opp-hz = /bits/ 64 <1100000000>; - ... - }; - }; -}; - -Example 6: opp-supported-hw +Example 5: opp-supported-hw (example: three level hierarchy of versions: cuts, substrate and process) / {
@@ -540,7 +482,7 @@ Example 6: opp-supported-hw }; }; -Example 7: opp-microvolt-<name>, opp-microamp-<name>: +Example 6: opp-microvolt-<name>, opp-microamp-<name>: (example: device with two possible microvolt ranges: slow and fast) / {
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4776): https://lists.cip-project.org/g/cip-dev/message/4776
Mute This Topic: https://lists.cip-project.org/mt/74768062/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 5/14 PM / OPP: Rename OPP nodes as opp@<opp-hz>
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit 754dcf35f34698661801ae1d391efa02affe83a7 upstream.
It would be better to name OPP nodes as opp@<opp-hz> as that will ensure that multiple DT nodes don't contain the same frequency. Of course we expect the writer to name the node with its opp-hz frequency and not any other frequency.
And that will let the compile error out if multiple nodes are using the same opp-hz frequency.
--- Documentation/devicetree/bindings/opp/opp.txt | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-)
Documentation/devicetree/bindings/opp/opp.txt +19 -19
@@ -177,20 +177,20 @@ Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together. compatible = "operating-points-v2"; opp-shared; - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>; opp-microamp = <70000>; clock-latency-ns = <300000>; opp-suspend; }; - opp01 { + opp@1100000000 { opp-hz = /bits/ 64 <1100000000>; opp-microvolt = <980000 1000000 1010000>; opp-microamp = <80000>; clock-latency-ns = <310000>; }; - opp02 { + opp@1200000000 { opp-hz = /bits/ 64 <1200000000>; opp-microvolt = <1025000>; clock-latency-ns = <290000>;
@@ -256,20 +256,20 @@ independently. * independently. */ - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>; opp-microamp = <70000>; clock-latency-ns = <300000>; opp-suspend; }; - opp01 { + opp@1100000000 { opp-hz = /bits/ 64 <1100000000>; opp-microvolt = <980000 1000000 1010000>; opp-microamp = <80000>; clock-latency-ns = <310000>; }; - opp02 { + opp@1200000000 { opp-hz = /bits/ 64 <1200000000>; opp-microvolt = <1025000>; opp-microamp = <90000;
@@ -332,20 +332,20 @@ DVFS state together. compatible = "operating-points-v2"; opp-shared; - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>; opp-microamp = <70000>; clock-latency-ns = <300000>; opp-suspend; }; - opp01 { + opp@1100000000 { opp-hz = /bits/ 64 <1100000000>; opp-microvolt = <980000 1000000 1010000>; opp-microamp = <80000>; clock-latency-ns = <310000>; }; - opp02 { + opp@1200000000 { opp-hz = /bits/ 64 <1200000000>; opp-microvolt = <1025000>; opp-microamp = <90000>;
@@ -358,20 +358,20 @@ DVFS state together. compatible = "operating-points-v2"; opp-shared; - opp10 { + opp@1300000000 { opp-hz = /bits/ 64 <1300000000>; opp-microvolt = <1045000 1050000 1055000>; opp-microamp = <95000>; clock-latency-ns = <400000>; opp-suspend; }; - opp11 { + opp@1400000000 { opp-hz = /bits/ 64 <1400000000>; opp-microvolt = <1075000>; opp-microamp = <100000>; clock-latency-ns = <400000>; }; - opp12 { + opp@1500000000 { opp-hz = /bits/ 64 <1500000000>; opp-microvolt = <1010000 1100000 1110000>; opp-microamp = <95000>;
@@ -398,7 +398,7 @@ Example 4: Handling multiple regulators compatible = "operating-points-v2"; opp-shared; - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000>, /* Supply 0 */ <960000>, /* Supply 1 */
@@ -411,7 +411,7 @@ Example 4: Handling multiple regulators /* OR */ - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>, /* Supply 0 */ <960000 965000 975000>, /* Supply 1 */
@@ -424,7 +424,7 @@ Example 4: Handling multiple regulators /* OR */ - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>, /* Supply 0 */ <960000 965000 975000>, /* Supply 1 */
@@ -456,7 +456,7 @@ Example 5: opp-supported-hw status = "okay"; opp-shared; - opp00 { + opp@600000000 { /* * Supports all substrate and process versions for 0xF * cuts, i.e. only first four cuts.
@@ -467,7 +467,7 @@ Example 5: opp-supported-hw ... }; - opp01 { + opp@800000000 { /* * Supports: * - cuts: only one, 6th cut (represented by 6th bit).
@@ -499,7 +499,7 @@ Example 6: opp-microvolt-<name>, opp-microamp-<name>: compatible = "operating-points-v2"; opp-shared; - opp00 { + opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt-slow = <900000 915000 925000>; opp-microvolt-fast = <970000 975000 985000>;
@@ -507,7 +507,7 @@ Example 6: opp-microvolt-<name>, opp-microamp-<name>: opp-microamp-fast = <71000>; }; - opp01 { + opp@1200000000 { opp-hz = /bits/ 64 <1200000000>; opp-microvolt-slow = <900000 915000 925000>, /* Supply vcc0 */ <910000 925000 935000>; /* Supply vcc1 */
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4778): https://lists.cip-project.org/g/cip-dev/message/4778
Mute This Topic: https://lists.cip-project.org/mt/74768064/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 6/14 PM / OPP: Add missing doc comments
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit dc4e7b1fa20a840d2317fcfdaa1064fc09d2afcb upstream.
Few doc-style comments were missing, add them. Rearrange another one to match the sequence within the structure.
--- drivers/base/power/opp/opp.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/base/power/opp/opp.h +3 -1
@@ -51,8 +51,8 @@ extern struct mutex dev_opp_list_lock;* are protected by the dev_opp_list_lock for integrity. * IMPORTANT: the opp nodes should be maintained in increasing * order. -* @dynamic: not-created from static DT entries. * @available: true/false - marks if this OPP as available or not +* @dynamic: not-created from static DT entries. * @turbo: true if turbo (boost) OPP * @suspend: true if suspend OPP * @rate: Frequency in hertz
@@ -126,7 +126,9 @@ struct device_list_opp {* @dev_list: list of devices that share these OPPs * @opp_list: list of opps * @np: struct device_node pointer for opp's DT node. +* @clock_latency_ns_max: Max clock latency in nanoseconds. * @shared_opp: OPP is shared between multiple devices. +* @suspend_opp: Pointer to OPP to be used during device suspend. * @dentry: debugfs dentry pointer of the real device directory (not links). * @dentry_name: Name of the real dentry. *
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4779): https://lists.cip-project.org/g/cip-dev/message/4779
Mute This Topic: https://lists.cip-project.org/mt/74768066/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 7/14 PM / OPP: Parse 'opp-supported-hw' binding
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit 7de36b0aa51a5a59e28fb2da768fa3ab07de0674 upstream.
OPP bindings allow a platform to enable OPPs based on the version of the hardware they are used for.
Add support to the OPP-core to parse these bindings, by introducing dev_pm_opp_{set|put}_supported_hw() APIs.
--- drivers/base/power/opp/core.c | 148 ++++++++++++++++++++++++++++++++++ drivers/base/power/opp/opp.h | 5 ++ include/linux/pm_opp.h | 13 +++ 3 files changed, 166 insertions(+)
drivers/base/power/opp/core.c +148 -0
@@ -559,6 +559,9 @@ static void _remove_device_opp(struct device_opp *dev_opp)if (!list_empty (&dev_opp->opp_list))return ; +if (dev_opp->supported_hw) +return ; + list_dev = list_first_entry(&dev_opp->dev_list, struct device_list_opp, node);
@@ -839,6 +842,145 @@ static int opp_parse_supplies(struct dev_pm_opp *opp, struct device *dev)return 0 ; } +/** +* dev_pm_opp_set_supported_hw() - Set supported platforms +* @dev: Device for which supported-hw has to be set. +* @versions: Array of hierarchy of versions to match. +* @count: Number of elements in the array. +* +* This is required only for the V2 bindings, and it enables a platform to +* specify the hierarchy of versions it supports. OPP layer will then enable +* OPPs, which are available for those versions, based on its 'opp-supported-hw' +* property. +* +* Locking: The internal device_opp and opp structures are RCU protected. +* Hence this function internally uses RCU updater strategy with mutex locks +* to keep the integrity of the internal data structures. Callers should ensure +* that this function is *NOT* called under RCU protection or in contexts where +* mutex cannot be locked. +*/ +int dev_pm_opp_set_supported_hw (struct device *dev,const u32 *versions, +unsigned int count) +{ +struct device_opp *dev_opp; +int ret =0 ; + +/* Hold our list modification lock here */ +mutex_lock (&dev_opp_list_lock); + + dev_opp =_add_device_opp (dev); +if (!dev_opp) { + ret = -ENOMEM ; + goto unlock; + } + +/* Make sure there are no concurrent readers while updating dev_opp */ +WARN_ON (!list_empty (&dev_opp->opp_list)); + +/* Do we already have a version hierarchy associated with dev_opp? */ +if (dev_opp->supported_hw) { +dev_err (dev,"%s: Already have supported hardware list\n" , + __func__); + ret = -EBUSY ; + goto err; + } + + dev_opp->supported_hw =kmemdup (versions, count *sizeof (*versions), +GFP_KERNEL ); +if (!dev_opp->supported_hw) { + ret = -ENOMEM ; + goto err; + } + + dev_opp->supported_hw_count = count; +mutex_unlock (&dev_opp_list_lock); +return 0 ; + +err: +_remove_device_opp (dev_opp); +unlock: +mutex_unlock (&dev_opp_list_lock); + +return ret; +} +EXPORT_SYMBOL_GPL (dev_pm_opp_set_supported_hw); + +/** +* dev_pm_opp_put_supported_hw() - Releases resources blocked for supported hw +* @dev: Device for which supported-hw has to be set. +* +* This is required only for the V2 bindings, and is called for a matching +* dev_pm_opp_set_supported_hw(). Until this is called, the device_opp structure +* will not be freed. +* +* Locking: The internal device_opp and opp structures are RCU protected. +* Hence this function internally uses RCU updater strategy with mutex locks +* to keep the integrity of the internal data structures. Callers should ensure +* that this function is *NOT* called under RCU protection or in contexts where +* mutex cannot be locked. +*/ +void dev_pm_opp_put_supported_hw (struct device *dev) +{ +struct device_opp *dev_opp; + +/* Hold our list modification lock here */ +mutex_lock (&dev_opp_list_lock); + +/* Check for existing list for 'dev' first */ + dev_opp =_find_device_opp (dev); +if (IS_ERR (dev_opp)) { +dev_err (dev,"Failed to find dev_opp: %ld\n" ,PTR_ERR (dev_opp)); + goto unlock; + } + +/* Make sure there are no concurrent readers while updating dev_opp */ +WARN_ON (!list_empty (&dev_opp->opp_list)); + +if (!dev_opp->supported_hw) { +dev_err (dev,"%s: Doesn't have supported hardware list\n" , + __func__); + goto unlock; + } + +kfree (dev_opp->supported_hw); + dev_opp->supported_hw =NULL ; + dev_opp->supported_hw_count =0 ; + +/* Try freeing device_opp if this was the last blocking resource */ +_remove_device_opp (dev_opp); + +unlock: +mutex_unlock (&dev_opp_list_lock); +} +EXPORT_SYMBOL_GPL (dev_pm_opp_put_supported_hw); + +static bool _opp_is_supported (struct device *dev,struct device_opp *dev_opp, +struct device_node *np) +{ +unsigned int count = dev_opp->supported_hw_count; +u32 version; +int ret; + +if (!dev_opp->supported_hw) +return true; + +while (count--) { + ret =of_property_read_u32_index (np,"opp-supported-hw" , count, + &version); +if (ret) { +dev_warn (dev,"%s: failed to read opp-supported-hw property at index %d: %d\n" , + __func__, count, ret); +return false; + } + +/* Both of these are bitwise masks of the versions */ +if (!(version & dev_opp->supported_hw[count])) +return false; + } + +return true; +} +/** * _opp_add_static_v2() - Allocate static OPPs (As per 'v2' DT bindings) * @dev: device for which we do this operation
@@ -885,6 +1027,12 @@ static int _opp_add_static_v2(struct device *dev, struct device_node *np) goto free_opp; } +/* Check if the OPP supports hardware's hierarchy of versions or not */ +if (!_opp_is_supported (dev, dev_opp, np)) { +dev_dbg (dev,"OPP not supported by hardware: %llu\n" , rate); + goto free_opp; + } +/* * Rate is defined as an unsigned long in clk API, and so casting * explicitly to its type. Must be fixed once rate is 64 bit
drivers/base/power/opp/opp.h +5 -0
@@ -129,6 +129,8 @@ struct device_list_opp {* @clock_latency_ns_max: Max clock latency in nanoseconds. * @shared_opp: OPP is shared between multiple devices. * @suspend_opp: Pointer to OPP to be used during device suspend. +* @supported_hw: Array of version number to support. +* @supported_hw_count: Number of elements in supported_hw array. * @dentry: debugfs dentry pointer of the real device directory (not links). * @dentry_name: Name of the real dentry. *
@@ -153,6 +155,9 @@ struct device_opp {bool shared_opp;struct dev_pm_opp *suspend_opp; +unsigned int *supported_hw; +unsigned int supported_hw_count; +#ifdef CONFIG_DEBUG_FS struct dentry *dentry;char dentry_name[NAME_MAX ];
include/linux/pm_opp.h +13 -0
@@ -55,6 +55,9 @@ int dev_pm_opp_enable(struct device *dev, unsigned long freq);int dev_pm_opp_disable (struct device *dev,unsigned long freq);struct srcu_notifier_head *dev_pm_opp_get_notifier (struct device *dev); +int dev_pm_opp_set_supported_hw (struct device *dev,const u32 *versions, +unsigned int count); +void dev_pm_opp_put_supported_hw (struct device *dev);#else static inline unsigned long dev_pm_opp_get_voltage (struct dev_pm_opp *opp) {
@@ -129,6 +132,16 @@ static inline struct srcu_notifier_head *dev_pm_opp_get_notifier( {return ERR_PTR (-EINVAL ); } + +static inline int dev_pm_opp_set_supported_hw (struct device *dev, +const u32 *versions, +unsigned int count) +{ +return -EINVAL ; +} + +static inline void dev_pm_opp_put_supported_hw (struct device *dev) {} +#endif /* CONFIG_PM_OPP */ #if defined(CONFIG_PM_OPP ) && defined(CONFIG_OF )
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4780): https://lists.cip-project.org/g/cip-dev/message/4780
Mute This Topic: https://lists.cip-project.org/mt/74768067/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 8/14 PM / OPP: Parse 'opp-<prop>-<name>' bindings
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit 01fb4d3c39d35b725441e8a9a26b3f3ad67793ed upstream. commit fd8d8e63467c922be9ae4452cca2980d473477d9 upstream squashed in.
OPP bindings (for few properties) allow a platform to choose a value/range among a set of available options. The options are present as opp-<prop>-<name>, where the platform needs to supply the <name> string.
The OPP properties which allow such an option are: opp-microvolt and opp-microamp.
Add support to the OPP-core to parse these bindings, by introducing dev_pm_opp_{set|put}_prop_name() APIs.
[wens: Squashed in Bartlomiej Zolnierkiewicz's <[email protected]>
upstream commit fd8d8e63467c922be9ae4452cca2980d473477d9 to fix a bug]
--- drivers/base/power/opp/core.c | 165 ++++++++++++++++++++++++++++++---- drivers/base/power/opp/opp.h | 2 + include/linux/pm_opp.h | 9 ++ 3 files changed, 161 insertions(+), 15 deletions(-)
drivers/base/power/opp/core.c +150 -15
@@ -562,6 +562,9 @@ static void _remove_device_opp(struct device_opp *dev_opp)if (dev_opp->supported_hw)return ; +if (dev_opp->prop_name) +return ; + list_dev = list_first_entry(&dev_opp->dev_list, struct device_list_opp, node);
@@ -794,35 +797,48 @@ unlock: }/* TODO: Support multiple regulators */ -static int opp_parse_supplies (struct dev_pm_opp *opp,struct device *dev) +static int opp_parse_supplies (struct dev_pm_opp *opp,struct device *dev, +struct device_opp *dev_opp) {u32 microvolt[3 ] = {0 };u32 val;int count, ret; +struct property *prop =NULL ; +char name[NAME_MAX ]; + +/* Search for "opp-microvolt-<name>" */ +if (dev_opp->prop_name) { +sprintf (name,"opp-microvolt-%s" , dev_opp->prop_name); + prop =of_find_property (opp->np, name,NULL ); + } + +if (!prop) { +/* Search for "opp-microvolt" */ +sprintf (name,"opp-microvolt" ); + prop =of_find_property (opp->np, name,NULL ); -/* Missing property isn't a problem, but an invalid entry is */ -if (!of_find_property (opp->np,"opp-microvolt" ,NULL )) -return 0 ; +/* Missing property isn't a problem, but an invalid entry is */ +if (!prop) +return 0 ; + } - count =of_property_count_u32_elems (opp->np,"opp-microvolt" ); + count =of_property_count_u32_elems (opp->np, name);if (count <0 ) { -dev_err (dev,"%s: Invalid opp-microvolt property (%d)\n" , - __func__, count); +dev_err (dev,"%s: Invalid %s property (%d)\n" , + __func__, name, count);return count; }/* There can be one or three elements here */ if (count !=1 && count !=3 ) { -dev_err (dev,"%s: Invalid number of elements in opp-microvolt property (%d)\n" , - __func__, count); +dev_err (dev,"%s: Invalid number of elements in %s property (%d)\n" , + __func__, name, count);return -EINVAL ; } - ret =of_property_read_u32_array (opp->np,"opp-microvolt" , microvolt, - count); + ret =of_property_read_u32_array (opp->np, name, microvolt, count);if (ret) { -dev_err (dev,"%s: error parsing opp-microvolt: %d\n" , __func__, - ret); +dev_err (dev,"%s: error parsing %s: %d\n" , __func__, name, ret);return -EINVAL ; }
@@ -836,7 +852,20 @@ static int opp_parse_supplies(struct dev_pm_opp *opp, struct device *dev) opp->u_volt_max = microvolt[2 ]; } -if (!of_property_read_u32 (opp->np,"opp-microamp" , &val)) +/* Search for "opp-microamp-<name>" */ + prop =NULL ; +if (dev_opp->prop_name) { +sprintf (name,"opp-microamp-%s" , dev_opp->prop_name); + prop =of_find_property (opp->np, name,NULL ); + } + +if (!prop) { +/* Search for "opp-microamp" */ +sprintf (name,"opp-microamp" ); + prop =of_find_property (opp->np, name,NULL ); + } + +if (prop && !of_property_read_u32 (opp->np, name, &val)) opp->u_amp = val;return 0 ;
@@ -954,6 +983,112 @@ unlock: }EXPORT_SYMBOL_GPL (dev_pm_opp_put_supported_hw); +/** +* dev_pm_opp_set_prop_name() - Set prop-extn name +* @dev: Device for which the regulator has to be set. +* @name: name to postfix to properties. +* +* This is required only for the V2 bindings, and it enables a platform to +* specify the extn to be used for certain property names. The properties to +* which the extension will apply are opp-microvolt and opp-microamp. OPP core +* should postfix the property name with -<name> while looking for them. +* +* Locking: The internal device_opp and opp structures are RCU protected. +* Hence this function internally uses RCU updater strategy with mutex locks +* to keep the integrity of the internal data structures. Callers should ensure +* that this function is *NOT* called under RCU protection or in contexts where +* mutex cannot be locked. +*/ +int dev_pm_opp_set_prop_name (struct device *dev,const char *name) +{ +struct device_opp *dev_opp; +int ret =0 ; + +/* Hold our list modification lock here */ +mutex_lock (&dev_opp_list_lock); + + dev_opp =_add_device_opp (dev); +if (!dev_opp) { + ret = -ENOMEM ; + goto unlock; + } + +/* Make sure there are no concurrent readers while updating dev_opp */ +WARN_ON (!list_empty (&dev_opp->opp_list)); + +/* Do we already have a prop-name associated with dev_opp? */ +if (dev_opp->prop_name) { +dev_err (dev,"%s: Already have prop-name %s\n" , __func__, + dev_opp->prop_name); + ret = -EBUSY ; + goto err; + } + + dev_opp->prop_name =kstrdup (name,GFP_KERNEL ); +if (!dev_opp->prop_name) { + ret = -ENOMEM ; + goto err; + } + +mutex_unlock (&dev_opp_list_lock); +return 0 ; + +err: +_remove_device_opp (dev_opp); +unlock: +mutex_unlock (&dev_opp_list_lock); + +return ret; +} +EXPORT_SYMBOL_GPL (dev_pm_opp_set_prop_name); + +/** +* dev_pm_opp_put_prop_name() - Releases resources blocked for prop-name +* @dev: Device for which the regulator has to be set. +* +* This is required only for the V2 bindings, and is called for a matching +* dev_pm_opp_set_prop_name(). Until this is called, the device_opp structure +* will not be freed. +* +* Locking: The internal device_opp and opp structures are RCU protected. +* Hence this function internally uses RCU updater strategy with mutex locks +* to keep the integrity of the internal data structures. Callers should ensure +* that this function is *NOT* called under RCU protection or in contexts where +* mutex cannot be locked. +*/ +void dev_pm_opp_put_prop_name (struct device *dev) +{ +struct device_opp *dev_opp; + +/* Hold our list modification lock here */ +mutex_lock (&dev_opp_list_lock); + +/* Check for existing list for 'dev' first */ + dev_opp =_find_device_opp (dev); +if (IS_ERR (dev_opp)) { +dev_err (dev,"Failed to find dev_opp: %ld\n" ,PTR_ERR (dev_opp)); + goto unlock; + } + +/* Make sure there are no concurrent readers while updating dev_opp */ +WARN_ON (!list_empty (&dev_opp->opp_list)); + +if (!dev_opp->prop_name) { +dev_err (dev,"%s: Doesn't have a prop-name\n" , __func__); + goto unlock; + } + +kfree (dev_opp->prop_name); + dev_opp->prop_name =NULL ; + +/* Try freeing device_opp if this was the last blocking resource */ +_remove_device_opp (dev_opp); + +unlock: +mutex_unlock (&dev_opp_list_lock); +} +EXPORT_SYMBOL_GPL (dev_pm_opp_put_prop_name); +static bool _opp_is_supported (struct device *dev,struct device_opp *dev_opp,struct device_node *np) {
@@ -1048,7 +1183,7 @@ static int _opp_add_static_v2(struct device *dev, struct device_node *np)if (!of_property_read_u32 (np,"clock-latency-ns" , &val)) new_opp->clock_latency_ns = val; - ret =opp_parse_supplies (new_opp, dev); + ret =opp_parse_supplies (new_opp, dev, dev_opp);if (ret) goto free_opp;
drivers/base/power/opp/opp.h +2 -0
@@ -131,6 +131,7 @@ struct device_list_opp {* @suspend_opp: Pointer to OPP to be used during device suspend. * @supported_hw: Array of version number to support. * @supported_hw_count: Number of elements in supported_hw array. +* @prop_name: A name to postfix to many DT properties, while parsing them. * @dentry: debugfs dentry pointer of the real device directory (not links). * @dentry_name: Name of the real dentry. *
@@ -157,6 +158,7 @@ struct device_opp {unsigned int *supported_hw;unsigned int supported_hw_count; +const char *prop_name;#ifdef CONFIG_DEBUG_FS struct dentry *dentry;
include/linux/pm_opp.h +9 -0
@@ -58,6 +58,8 @@ struct srcu_notifier_head *dev_pm_opp_get_notifier(struct device *dev);int dev_pm_opp_set_supported_hw (struct device *dev,const u32 *versions,unsigned int count);void dev_pm_opp_put_supported_hw (struct device *dev); +int dev_pm_opp_set_prop_name (struct device *dev,const char *name); +void dev_pm_opp_put_prop_name (struct device *dev);#else static inline unsigned long dev_pm_opp_get_voltage (struct dev_pm_opp *opp) {
@@ -142,6 +144,13 @@ static inline int dev_pm_opp_set_supported_hw(struct device *dev,static inline void dev_pm_opp_put_supported_hw (struct device *dev) {} +static inline int dev_pm_opp_set_prop_name (struct device *dev,const char *name) +{ +return -EINVAL ; +} + +static inline void dev_pm_opp_put_prop_name (struct device *dev) {} +#endif /* CONFIG_PM_OPP */ #if defined(CONFIG_PM_OPP ) && defined(CONFIG_OF )
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4781): https://lists.cip-project.org/g/cip-dev/message/4781
Mute This Topic: https://lists.cip-project.org/mt/74768068/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 9/14 PM / OPP: Set cpu_dev->id in cpumask first
In reply to Chen-Yu Tsai (Moxa)From: Pi-Cheng Chen <[email protected]>
commit d9de19b1cc013433ad293365b5b3902ec73dfd60 upstream.
Set cpu_dev->id in cpumask first when setting up cpumask for CPUs that share the same OPP table. This might be helpful when handling cpumask without the original CPU bitfield set.
--- drivers/base/power/opp/cpu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/base/power/opp/cpu.c +2 -1
@@ -218,7 +218,6 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_of_cpumask_add_table);/* * Works only for OPP v2 bindings. * -* cpumask should be already set to mask of cpu_dev->id. * Returns -ENOENT if operating-points-v2 bindings aren't supported. */ int dev_pm_opp_of_get_sharing_cpus (struct device *cpu_dev,cpumask_var_t cpumask)
@@ -234,6 +233,8 @@ int dev_pm_opp_of_get_sharing_cpus(struct device *cpu_dev, cpumask_var_t cpumaskreturn -ENOENT ; } +cpumask_set_cpu (cpu_dev->id, cpumask); +/* OPPs are shared ? */ if (!of_property_read_bool (np,"opp-shared" )) goto put_cpu_node;
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4782): https://lists.cip-project.org/g/cip-dev/message/4782
Mute This Topic: https://lists.cip-project.org/mt/74768069/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 10/14 PM / OPP: Use snprintf() instead of sprintf()
In reply to Chen-Yu Tsai (Moxa)From: Viresh Kumar <[email protected]>
commit 5ff24d601092b222340b28466e263b1c4559407e upstream.
sprintf() can access memory outside of the range of the character array, and is risky in some situations. The driver specified prop_name string can be longer than NAME_MAX here (only an attacker will do that though) and so blindly copying it into the character array of size NAME_MAX isn't safe. Instead we must use snprintf() here.
--- drivers/base/power/opp/core.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/base/power/opp/core.c +4 -2
@@ -808,7 +808,8 @@ static int opp_parse_supplies(struct dev_pm_opp *opp, struct device *dev,/* Search for "opp-microvolt-<name>" */ if (dev_opp->prop_name) { -sprintf (name,"opp-microvolt-%s" , dev_opp->prop_name); +snprintf (name,sizeof (name),"opp-microvolt-%s" , + dev_opp->prop_name); prop =of_find_property (opp->np, name,NULL ); }
@@ -855,7 +856,8 @@ static int opp_parse_supplies(struct dev_pm_opp *opp, struct device *dev,/* Search for "opp-microamp-<name>" */ prop =NULL ;if (dev_opp->prop_name) { -sprintf (name,"opp-microamp-%s" , dev_opp->prop_name); +snprintf (name,sizeof (name),"opp-microamp-%s" , + dev_opp->prop_name); prop =of_find_property (opp->np, name,NULL ); }
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4786): https://lists.cip-project.org/g/cip-dev/message/4786
Mute This Topic: https://lists.cip-project.org/mt/74768073/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 11/14 devicetree: bindings: Add optional dynamic-power-coefficient property
In reply to Chen-Yu Tsai (Moxa)From: Punit Agrawal <[email protected]>
commit 3be3f8f36e7349006f19c8c8f0d686e98462a993 upstream.
The dynamic power consumption of a device is proportional to the square of voltage (V) and the clock frequency (f). It can be expressed as
Pdyn = dynamic-power-coefficient * V^2 * f.
The coefficient represents the running time dynamic power consumption in units of mw/MHz/uVolt^2 and can be used in the above formula to calculate the dynamic power in mW.
--- Documentation/devicetree/bindings/arm/cpus.txt | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
Documentation/devicetree/bindings/arm/cpus.txt +17 -0
@@ -243,6 +243,23 @@ nodes to be present and contain the properties described below. Definition: Specifies the syscon node controlling the cpu core power domains. + - dynamic-power-coefficient + Usage: optional + Value type: <prop-encoded-array> + Definition: A u32 value that represents the running time dynamic + power coefficient in units of mW/MHz/uVolt^2. The + coefficient can either be calculated from power + measurements or derived by analysis. + + The dynamic power consumption of the CPU is + proportional to the square of the Voltage (V) and + the clock frequency (f). The coefficient is used to + calculate the dynamic power as below - + + Pdyn = dynamic-power-coefficient * V^2 * f + + where voltage is in uV, frequency is in MHz. + Example 1 (dual-cluster big.LITTLE system 32-bit): cpus {
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4785): https://lists.cip-project.org/g/cip-dev/message/4785
Mute This Topic: https://lists.cip-project.org/mt/74768072/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 12/14 cpufreq-dt: Supply power coefficient when registering cooling devices
In reply to Chen-Yu Tsai (Moxa)From: Punit Agrawal <[email protected]>
commit f8fa8ae06b8c2c25d81c99766f9226adc5c3e073 upstream.
Support registering cooling devices with dynamic power coefficient where provided by the device tree. This allows OF registered cooling devices driver to be used with the power_allocator thermal governor.
--- drivers/cpufreq/cpufreq-dt.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/cpufreq/cpufreq-dt.c +7 -2
@@ -407,8 +407,13 @@ static void cpufreq_ready(struct cpufreq_policy *policy)* thermal DT code takes care of matching them. */ if (of_find_property (np,"#cooling-cells" ,NULL )) { - priv->cdev =of_cpufreq_cooling_register (np, - policy->related_cpus); +u32 power_coefficient =0 ; + +of_property_read_u32 (np,"dynamic-power-coefficient" , + &power_coefficient); + + priv->cdev =of_cpufreq_power_cooling_register (np, + policy->related_cpus, power_coefficient,NULL );if (IS_ERR (priv->cdev)) { dev_err(priv->cpu_dev, "running cpufreq without cooling device: %ld\n",
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4783): https://lists.cip-project.org/g/cip-dev/message/4783
Mute This Topic: https://lists.cip-project.org/mt/74768070/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 13/14 cpufreq-dt: fix handling regulator_get_voltage() result
In reply to Chen-Yu Tsai (Moxa)From: Andrzej Hajda <[email protected]>
commit 929ca89c305a6ed7a4149115be99af6d73c36918 upstream.
The function can return negative values so it should be assigned to signed type.
The problem has been detected using proposed semantic patch scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci.
--- drivers/cpufreq/cpufreq-dt.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/cpufreq/cpufreq-dt.c +3 -2
@@ -50,7 +50,8 @@ static int set_target(struct cpufreq_policy *policy, unsigned int index)struct private_data *priv = policy->driver_data;struct device *cpu_dev = priv->cpu_dev;struct regulator *cpu_reg = priv->cpu_reg; -unsigned long volt =0 , volt_old =0 , tol =0 ; +unsigned long volt =0 , tol =0 ; +int volt_old =0 ;unsigned int old_freq, new_freq;long freq_Hz, freq_exact;int ret;
@@ -83,7 +84,7 @@ static int set_target(struct cpufreq_policy *policy, unsigned int index) opp_freq / 1000, volt); } -dev_dbg (cpu_dev,"%u MHz, %ld mV --> %u MHz, %ld mV\n" , +dev_dbg (cpu_dev,"%u MHz, %d mV --> %u MHz, %ld mV\n" , old_freq /1000 , (volt_old >0 ) ? volt_old /1000 :-1 , new_freq /1000 , volt ? volt /1000 :-1 );
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4787): https://lists.cip-project.org/g/cip-dev/message/4787
Mute This Topic: https://lists.cip-project.org/mt/74768074/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
PATCH v3 14/14 cpufreq: cpufreq-dt: avoid uninitialized variable warnings:
In reply to Chen-Yu Tsai (Moxa)From: Arnd Bergmann <[email protected]>
commit b331bc20d9281213f7fb67912638e0fb5baeb324 upstream.
gcc warns quite a bit about values returned from allocate_resources() in cpufreq-dt.c:
cpufreq-dt.c: In function 'cpufreq_init':
cpufreq-dt.c:327:6: error: 'cpu_dev' may be used uninitialized in this function [-Werror=maybe-uninitialized] cpufreq-dt.c:197:17: note: 'cpu_dev' was declared here
cpufreq-dt.c:376:2: error: 'cpu_clk' may be used uninitialized in this function [-Werror=maybe-uninitialized] cpufreq-dt.c:199:14: note: 'cpu_clk' was declared herecpufreq-dt.c: In function 'dt_cpufreq_probe':
cpufreq-dt.c:461:2: error: 'cpu_clk' may be used uninitialized in this function [-Werror=maybe-uninitialized] cpufreq-dt.c:447:14: note: 'cpu_clk' was declared here
The problem is that it's slightly hard for gcc to follow return codes across PTR_ERR() calls.
This patch uses explicit assignments to the "ret" variable to make it easier for gcc to verify that the code is actually correct, without the need to add a bogus initialization.
--- drivers/cpufreq/cpufreq-dt.c | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-)
drivers/cpufreq/cpufreq-dt.c +7 -8
@@ -142,15 +142,16 @@ static int allocate_resources(int cpu, struct device **cdev, try_again: cpu_reg =regulator_get_optional (cpu_dev, reg); -if (IS_ERR (cpu_reg)) { + ret =PTR_ERR_OR_ZERO (cpu_reg); +if (ret) {/* * If cpu's regulator supply node is present, but regulator is * not yet registered, we should try defering probe. */ -if (PTR_ERR (cpu_reg) == -EPROBE_DEFER ) { +if (ret == -EPROBE_DEFER ) {dev_dbg (cpu_dev,"cpu%d regulator not ready, retry\n" , cpu); -return -EPROBE_DEFER ; +return ret; }/* Try with "cpu-supply" */
@@ -159,18 +160,16 @@ try_again: goto try_again; } -dev_dbg (cpu_dev,"no regulator for cpu%d: %ld\n" , - cpu,PTR_ERR (cpu_reg)); +dev_dbg (cpu_dev,"no regulator for cpu%d: %d\n" , cpu, ret); } cpu_clk =clk_get (cpu_dev,NULL ); -if (IS_ERR (cpu_clk)) { + ret =PTR_ERR_OR_ZERO (cpu_clk); +if (ret) {/* put regulator */ if (!IS_ERR (cpu_reg))regulator_put (cpu_reg); - ret =PTR_ERR (cpu_clk); -/* * If cpu's clk node is present, but clock is not yet * registered, we should try defering probe.
Signature · 1 line
2.27.0.rc0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4784): https://lists.cip-project.org/g/cip-dev/message/4784
Mute This Topic: https://lists.cip-project.org/mt/74768071/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Hi!
Quoted 10 lines
This is v3 of the part 1 of MOXA's PM / OPP / cpufreq backport series. Changes since v2:
- Squashed "PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties" into "PM / OPP: Parse 'opp-<prop>-<name>' bindings"
Changes since v1:
- Added missing SoB and upstream commit hash for "PM / OPP: Set
cpu_dev->id in cpumask first"
Thanks! I have applied the series, will run some basic tests and push the results if they work okay.
Best regards,
Pavel
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4790): https://lists.cip-project.org/g/cip-dev/message/4790
Mute This Topic: https://lists.cip-project.org/mt/74768055/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-