From: Viresh Kumar <viresh.kumar@...> 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 i

From: Viresh Kumar <viresh.kumar@...> commit 1c4d12de2719dfdf27c6dab31e7a5641ee293c94 upstream. We may want to enable only a subset of OPPs, from the bigger list of OPPs, based on what version

From: Viresh Kumar <viresh.kumar@...> commit 754dcf35f34698661801ae1d391efa02affe83a7 upstream. It would be better to name OPP nodes as opp@<opp-hz> as that will ensure that multiple DT nodes d

From: Viresh Kumar <viresh.kumar@...> commit dc4e7b1fa20a840d2317fcfdaa1064fc09d2afcb upstream. Few doc-style comments were missing, add them. Rearrange another one to match the sequence within

From: Viresh Kumar <viresh.kumar@...> commit 7de36b0aa51a5a59e28fb2da768fa3ab07de0674 upstream. OPP bindings allow a platform to enable OPPs based on the version of the hardware they are used f

From: Viresh Kumar <viresh.kumar@...> commit 01fb4d3c39d35b725441e8a9a26b3f3ad67793ed upstream. commit fd8d8e63467c922be9ae4452cca2980d473477d9 upstream squashed in. OPP bindings (for few prope

From: Pi-Cheng Chen <pi-cheng.chen@...> commit d9de19b1cc013433ad293365b5b3902ec73dfd60 upstream. Set cpu_dev->id in cpumask first when setting up cpumask for CPUs that share the same OPP table

From: Punit Agrawal <punit.agrawal@...> commit f8fa8ae06b8c2c25d81c99766f9226adc5c3e073 upstream. Support registering cooling devices with dynamic power coefficient where provided by the device tr

From: Arnd Bergmann <arnd@...> commit b331bc20d9281213f7fb67912638e0fb5baeb324 upstream. gcc warns quite a bit about values returned from allocate_resources() in cpufreq-dt.c: cpufreq-dt.c: In fu

From: Punit Agrawal <punit.agrawal@...> commit 3be3f8f36e7349006f19c8c8f0d686e98462a993 upstream. The dynamic power consumption of a device is proportional to the square of voltage (V) and the clo

From: Viresh Kumar <viresh.kumar@...> commit 5ff24d601092b222340b28466e263b1c4559407e upstream. sprintf() can access memory outside of the range of the character array, and is risky in some sit

From: Andrzej Hajda <a.hajda@...> commit 929ca89c305a6ed7a4149115be99af6d73c36918 upstream. The function can return negative values so it should be assigned to signed type. The problem has bee

From: Viresh Kumar <viresh.kumar@...> commit 655c9df961751ce21466f6e97e8033932c27a675 upstream. In few use cases (like: cpufreq), it is desired to get the maximum voltage latency for changing O

From: Viresh Kumar <viresh.kumar@...> commit 9f8ea969d5cfdd4353d2adb004e8e2286b984369 upstream. This allows the OPP core to request/free the regulator resource, attached to a device OPP. The re

From: Viresh Kumar <viresh.kumar@...> commit 2174344765f472895c076d703c9cdc58215e1393 upstream. In few use cases (like: cpufreq), it is desired to get the maximum latency for changing OPPs. Add

From: Viresh Kumar <viresh.kumar@...> commit 7d34d56ef3349cd5f29cf7aab6650f3414fa81b9 upstream. Disable any OPPs where the connected regulator isn't able to provide the specified voltage. Signe

Hi everyone, This is part 2 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 S

From: Viresh Kumar <viresh.kumar@...> commit 50f8cfbd5897ca182d43f4caf19937153f17a604 uptream. V2 bindings have better support for clock-latency and voltage-tolerance and doesn't need special c

From: Viresh Kumar <viresh.kumar@...> commit 6a0712f6f199e737aa5913d28ec4bd3a25de9660 upstream. This adds a routine, dev_pm_opp_set_rate(), responsible for configuring power-supply and clock so

From: Viresh Kumar <viresh.kumar@...> commit d54974c2513f487e9e70fbdc79c5da51c53e23da upstream. OPP core has got almost everything now to manage device's OPP transitions, the only thing left is