Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ae982073 authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'pm+acpi-4.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm 

Pull power management and ACPI updates from Rafael Wysocki:
 "From the number of commits perspective, the biggest items are ACPICA
  and cpufreq changes with the latter taking the lead (over 50 commits).

  On the cpufreq front, there are many cleanups and minor fixes in the
  core and governors, driver updates etc.  We also have a new cpufreq
  driver for Mediatek MT8173 chips.

  ACPICA mostly updates its debug infrastructure and adds a number of
  fixes and cleanups for a good measure.

  The Operating Performance Points (OPP) framework is updated with new
  DT bindings and support for them among other things.

  We have a few updates of the generic power domains framework and a
  reorganization of the ACPI device enumeration code and bus type
  operations.

  And a lot of fixes and cleanups all over.

  Included is one branch from the MFD tree as it contains some
  PM-related driver core and ACPI PM changes a few other commits are
  based on.

  Specifics:

   - ACPICA update to upstream revision 20150818 including method
     tracing extensions to allow more in-depth AML debugging in the
     kernel and a number of assorted fixes and cleanups (Bob Moore, Lv
     Zheng, Markus Elfring).

   - ACPI sysfs code updates and a documentation update related to AML
     method tracing (Lv Zheng).

   - ACPI EC driver fix related to serialized evaluations of _Qxx
     methods and ACPI tools updates allowing the EC userspace tool to be
     built from the kernel source (Lv Zheng).

   - ACPI processor driver updates preparing it for future introduction
     of CPPC support and ACPI PCC mailbox driver updates (Ashwin
     Chaugule).

   - ACPI interrupts enumeration fix for a regression related to the
     handling of IRQ attribute conflicts between MADT and the ACPI
     namespace (Jiang Liu).

   - Fixes related to ACPI device PM (Mika Westerberg, Srinidhi
     Kasagar).

   - ACPI device registration code reorganization to separate the
     sysfs-related code and bus type operations from the rest (Rafael J
     Wysocki).

   - Assorted cleanups in the ACPI core (Jarkko Nikula, Mathias Krause,
     Andy Shevchenko, Rafael J Wysocki, Nicolas Iooss).

   - ACPI cpufreq driver and ia64 cpufreq driver fixes and cleanups (Pan
     Xinhui, Rafael J Wysocki).

   - cpufreq core cleanups on top of the previous changes allowing it to
     preseve its sysfs directories over system suspend/resume (Viresh
     Kumar, Rafael J Wysocki, Sebastian Andrzej Siewior).

   - cpufreq fixes and cleanups related to governors (Viresh Kumar).

   - cpufreq updates (core and the cpufreq-dt driver) related to the
     turbo/boost mode support (Viresh Kumar, Bartlomiej Zolnierkiewicz).

   - New DT bindings for Operating Performance Points (OPP), support for
     them in the OPP framework and in the cpufreq-dt driver plus related
     OPP framework fixes and cleanups (Viresh Kumar).

   - cpufreq powernv driver updates (Shilpasri G Bhat).

   - New cpufreq driver for Mediatek MT8173 (Pi-Cheng Chen).

   - Assorted cpufreq driver (speedstep-lib, sfi, integrator) cleanups
     and fixes (Abhilash Jindal, Andrzej Hajda, Cristian Ardelean).

   - intel_pstate driver updates including Skylake-S support, support
     for enabling HW P-states per CPU and an additional vendor bypass
     list entry (Kristen Carlson Accardi, Chen Yu, Ethan Zhao).

   - cpuidle core fixes related to the handling of coupled idle states
     (Xunlei Pang).

   - intel_idle driver updates including Skylake Client support and
     support for freeze-mode-specific idle states (Len Brown).

   - Driver core updates related to power management (Andy Shevchenko,
     Rafael J Wysocki).

   - Generic power domains framework fixes and cleanups (Jon Hunter,
     Geert Uytterhoeven, Rajendra Nayak, Ulf Hansson).

   - Device PM QoS framework update to allow the latency tolerance
     setting to be exposed to user space via sysfs (Mika Westerberg).

   - devfreq support for PPMUv2 in Exynos5433 and a fix for an incorrect
     exynos-ppmu DT binding (Chanwoo Choi, Javier Martinez Canillas).

   - System sleep support updates (Alan Stern, Len Brown, SungEun Kim).

   - rockchip-io AVS support updates (Heiko Stuebner).

   - PM core clocks support fixup (Colin Ian King).

   - Power capping RAPL driver update including support for Skylake H/S
     and Broadwell-H (Radivoje Jovanovic, Seiichi Ikarashi).

   - Generic device properties framework fixes related to the handling
     of static (driver-provided) property sets (Andy Shevchenko).

   - turbostat and cpupower updates (Len Brown, Shilpasri G Bhat,
     Shreyas B Prabhu)"

* tag 'pm+acpi-4.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (180 commits)
  cpufreq: speedstep-lib: Use monotonic clock
  cpufreq: powernv: Increase the verbosity of OCC console messages
  cpufreq: sfi: use kmemdup rather than duplicating its implementation
  cpufreq: drop !cpufreq_driver check from cpufreq_parse_governor()
  cpufreq: rename cpufreq_real_policy as cpufreq_user_policy
  cpufreq: remove redundant 'policy' field from user_policy
  cpufreq: remove redundant 'governor' field from user_policy
  cpufreq: update user_policy.* on success
  cpufreq: use memcpy() to copy policy
  cpufreq: remove redundant CPUFREQ_INCOMPATIBLE notifier event
  cpufreq: mediatek: Add MT8173 cpufreq driver
  dt-bindings: mediatek: Add MT8173 CPU DVFS clock bindings
  PM / Domains: Fix typo in description of genpd_dev_pm_detach()
  PM / Domains: Remove unusable governor dummies
  PM / Domains: Make pm_genpd_init() available to modules
  PM / domains: Align column headers and data in pm_genpd_summary output
  powercap / RAPL: disable the 2nd power limit properly
  tools: cpupower: Fix error when running cpupower monitor
  PM / OPP: Drop unlikely before IS_ERR(_OR_NULL)
  PM / OPP: Fix static checker warning (broken 64bit big endian systems)
  ...
parents f1a3c0b9 e625ccec

Documentation/acpi/method-tracing.txt

+185 −19
Original line number Original line Diff line number Diff line 
/sys/module/acpi/parameters/:

ACPICA Trace Facility



Copyright (C) 2015, Intel Corporation

Author: Lv Zheng <lv.zheng@intel.com>





Abstract:



This document describes the functions and the interfaces of the method

tracing facility.



1. Functionalities and usage examples:



   ACPICA provides method tracing capability. And two functions are

   currently implemented using this capability.



   A. Log reducer

   ACPICA subsystem provides debugging outputs when CONFIG_ACPI_DEBUG is

   enabled. The debugging messages which are deployed via

   ACPI_DEBUG_PRINT() macro can be reduced at 2 levels - per-component

   level (known as debug layer, configured via

   /sys/module/acpi/parameters/debug_layer) and per-type level (known as

   debug level, configured via /sys/module/acpi/parameters/debug_level).



   But when the particular layer/level is applied to the control method

   evaluations, the quantity of the debugging outputs may still be too

   large to be put into the kernel log buffer. The idea thus is worked out

   to only enable the particular debug layer/level (normally more detailed)

   logs when the control method evaluation is started, and disable the

   detailed logging when the control method evaluation is stopped.



   The following command examples illustrate the usage of the "log reducer"

   functionality:

   a. Filter out the debug layer/level matched logs when control methods

      are being evaluated:

      # cd /sys/module/acpi/parameters

      # echo "0xXXXXXXXX" > trace_debug_layer

      # echo "0xYYYYYYYY" > trace_debug_level

      # echo "enable" > trace_state

   b. Filter out the debug layer/level matched logs when the specified

      control method is being evaluated:

      # cd /sys/module/acpi/parameters

      # echo "0xXXXXXXXX" > trace_debug_layer

      # echo "0xYYYYYYYY" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "method" > /sys/module/acpi/parameters/trace_state

   c. Filter out the debug layer/level matched logs when the specified

      control method is being evaluated for the first time:

      # cd /sys/module/acpi/parameters

      # echo "0xXXXXXXXX" > trace_debug_layer

      # echo "0xYYYYYYYY" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "method-once" > /sys/module/acpi/parameters/trace_state

   Where:

      0xXXXXXXXX/0xYYYYYYYY: Refer to Documentation/acpi/debug.txt for

			     possible debug layer/level masking values.

      \PPPP.AAAA.TTTT.HHHH: Full path of a control method that can be found

			    in the ACPI namespace. It needn't be an entry

			    of a control method evaluation.



   B. AML tracer



   There are special log entries added by the method tracing facility at

   the "trace points" the AML interpreter starts/stops to execute a control

   method, or an AML opcode. Note that the format of the log entries are

   subject to change:

     [    0.186427]   exdebug-0398 ex_trace_point        : Method Begin [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution.

     [    0.186630]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905c88:If] execution.

     [    0.186820]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905cc0:LEqual] execution.

     [    0.187010]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905a20:-NamePath-] execution.

     [    0.187214]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905a20:-NamePath-] execution.

     [    0.187407]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905f60:One] execution.

     [    0.187594]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905f60:One] execution.

     [    0.187789]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905cc0:LEqual] execution.

     [    0.187980]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905cc0:Return] execution.

     [    0.188146]   exdebug-0398 ex_trace_point        : Opcode Begin [0xf5905f60:One] execution.

     [    0.188334]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905f60:One] execution.

     [    0.188524]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905cc0:Return] execution.

     [    0.188712]   exdebug-0398 ex_trace_point        : Opcode End [0xf5905c88:If] execution.

     [    0.188903]   exdebug-0398 ex_trace_point        : Method End [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution.



   Developers can utilize these special log entries to track the AML

   interpretion, thus can aid issue debugging and performance tuning. Note

   that, as the "AML tracer" logs are implemented via ACPI_DEBUG_PRINT()

   macro, CONFIG_ACPI_DEBUG is also required to be enabled for enabling

   "AML tracer" logs.



   The following command examples illustrate the usage of the "AML tracer"

   functionality:

   a. Filter out the method start/stop "AML tracer" logs when control

      methods are being evaluated:

      # cd /sys/module/acpi/parameters

      # echo "0x80" > trace_debug_layer

      # echo "0x10" > trace_debug_level

      # echo "enable" > trace_state

   b. Filter out the method start/stop "AML tracer" when the specified

      control method is being evaluated:

      # cd /sys/module/acpi/parameters

      # echo "0x80" > trace_debug_layer

      # echo "0x10" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "method" > trace_state

   c. Filter out the method start/stop "AML tracer" logs when the specified

      control method is being evaluated for the first time:

      # cd /sys/module/acpi/parameters

      # echo "0x80" > trace_debug_layer

      # echo "0x10" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "method-once" > trace_state

   d. Filter out the method/opcode start/stop "AML tracer" when the

      specified control method is being evaluated:

      # cd /sys/module/acpi/parameters

      # echo "0x80" > trace_debug_layer

      # echo "0x10" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "opcode" > trace_state

   e. Filter out the method/opcode start/stop "AML tracer" when the

      specified control method is being evaluated for the first time:

      # cd /sys/module/acpi/parameters

      # echo "0x80" > trace_debug_layer

      # echo "0x10" > trace_debug_level

      # echo "\PPPP.AAAA.TTTT.HHHH" > trace_method_name

      # echo "opcode-opcode" > trace_state



  Note that all above method tracing facility related module parameters can

  be used as the boot parameters, for example:

      acpi.trace_debug_layer=0x80 acpi.trace_debug_level=0x10 \

      acpi.trace_method_name=\_SB.LID0._LID acpi.trace_state=opcode-once



2. Interface descriptions:



   All method tracing functions can be configured via ACPI module

   parameters that are accessible at /sys/module/acpi/parameters/:





   trace_method_name

   trace_method_name

	The AML method name that the user wants to trace

	The full path of the AML method that the user wants to trace.

	Note that the full path shouldn't contain the trailing "_"s in its

	name segments but may contain "\" to form an absolute path.





   trace_debug_layer

   trace_debug_layer

	The temporary debug_layer used when tracing the method.

	The temporary debug_layer used when the tracing feature is enabled.

	Using 0xffffffff by default if it is 0.

	Using ACPI_EXECUTER (0x80) by default, which is the debug_layer

	used to match all "AML tracer" logs.





   trace_debug_level

   trace_debug_level

	The temporary debug_level used when tracing the method.

	The temporary debug_level used when the tracing feature is enabled.

	Using 0x00ffffff by default if it is 0.

	Using ACPI_LV_TRACE_POINT (0x10) by default, which is the

	debug_level used to match all "AML tracer" logs.





   trace_state

   trace_state

	The status of the tracing feature.

	The status of the tracing feature.



	Users can enable/disable this debug tracing feature by executing

	"enabled" means this feature is enabled

	the following command:

	and the AML method is traced every time it's executed.

	    # echo string > /sys/module/acpi/parameters/trace_state



	Where "string" should be one of the followings:

	"1" means this feature is enabled and the AML method

	"disable"

	will only be traced during the next execution.

	    Disable the method tracing feature.



	"enable"

	"disabled" means this feature is disabled.

	    Enable the method tracing feature.

	Users can enable/disable this debug tracing feature by

	    ACPICA debugging messages matching

	"echo string > /sys/module/acpi/parameters/trace_state".

	    "trace_debug_layer/trace_debug_level" during any method

	"string" should be one of "enable", "disable" and "1".
 
	    execution will be logged.

	"method"

	    Enable the method tracing feature.

	    ACPICA debugging messages matching

	    "trace_debug_layer/trace_debug_level" during method execution

	    of "trace_method_name" will be logged.

	"method-once"

	    Enable the method tracing feature.

	    ACPICA debugging messages matching

	    "trace_debug_layer/trace_debug_level" during method execution

	    of "trace_method_name" will be logged only once.

	"opcode"

	    Enable the method tracing feature.

	    ACPICA debugging messages matching

	    "trace_debug_layer/trace_debug_level" during method/opcode

	    execution of "trace_method_name" will be logged.

	"opcode-once"

	    Enable the method tracing feature.

	    ACPICA debugging messages matching

	    "trace_debug_layer/trace_debug_level" during method/opcode

	    execution of "trace_method_name" will be logged only once.

	Note that, the difference between the "enable" and other feature

        enabling options are:

	1. When "enable" is specified, since

	   "trace_debug_layer/trace_debug_level" shall apply to all control

	   method evaluations, after configuring "trace_state" to "enable",

	   "trace_method_name" will be reset to NULL.

	2. When "method/opcode" is specified, if

	   "trace_method_name" is NULL when "trace_state" is configured to

	   these options, the "trace_debug_layer/trace_debug_level" will

	   apply to all control method evaluations.

Documentation/cpu-freq/core.txt

+2 −5
Original line number Original line Diff line number Diff line
@@ -55,16 +55,13 @@ transition notifiers. 
----------------------------

----------------------------





These are notified when a new policy is intended to be set. Each

These are notified when a new policy is intended to be set. Each

CPUFreq policy notifier is called three times for a policy transition:

CPUFreq policy notifier is called twice for a policy transition:





1.) During CPUFREQ_ADJUST all CPUFreq notifiers may change the limit if

1.) During CPUFREQ_ADJUST all CPUFreq notifiers may change the limit if

    they see a need for this - may it be thermal considerations or

    they see a need for this - may it be thermal considerations or

    hardware limitations.

    hardware limitations.





2.) During CPUFREQ_INCOMPATIBLE only changes may be done in order to avoid

2.) And during CPUFREQ_NOTIFY all notifiers are informed of the new policy

    hardware failure.



3.) And during CPUFREQ_NOTIFY all notifiers are informed of the new policy

   - if two hardware drivers failed to agree on a new policy before this

   - if two hardware drivers failed to agree on a new policy before this

   stage, the incompatible hardware shall be shut down, and the user

   stage, the incompatible hardware shall be shut down, and the user

   informed of this.

   informed of this.

Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt

0 → 100644
+83 −0
Original line number Original line Diff line number Diff line 
Device Tree Clock bindins for CPU DVFS of Mediatek MT8173 SoC



Required properties:

- clocks: A list of phandle + clock-specifier pairs for the clocks listed in clock names.

- clock-names: Should contain the following:

	"cpu"		- The multiplexer for clock input of CPU cluster.

	"intermediate"	- A parent of "cpu" clock which is used as "intermediate" clock

			  source (usually MAINPLL) when the original CPU PLL is under

			  transition and not stable yet.

	Please refer to Documentation/devicetree/bindings/clk/clock-bindings.txt for

	generic clock consumer properties.

- proc-supply: Regulator for Vproc of CPU cluster.



Optional properties:

- sram-supply: Regulator for Vsram of CPU cluster. When present, the cpufreq driver

	       needs to do "voltage tracking" to step by step scale up/down Vproc and

	       Vsram to fit SoC specific needs. When absent, the voltage scaling

	       flow is handled by hardware, hence no software "voltage tracking" is

	       needed.



Example:

--------

	cpu0: cpu@0 {

		device_type = "cpu";

		compatible = "arm,cortex-a53";

		reg = <0x000>;

		enable-method = "psci";

		cpu-idle-states = <&CPU_SLEEP_0>;

		clocks = <&infracfg CLK_INFRA_CA53SEL>,

			 <&apmixedsys CLK_APMIXED_MAINPLL>;

		clock-names = "cpu", "intermediate";

	};



	cpu1: cpu@1 {

		device_type = "cpu";

		compatible = "arm,cortex-a53";

		reg = <0x001>;

		enable-method = "psci";

		cpu-idle-states = <&CPU_SLEEP_0>;

		clocks = <&infracfg CLK_INFRA_CA53SEL>,

			 <&apmixedsys CLK_APMIXED_MAINPLL>;

		clock-names = "cpu", "intermediate";

	};



	cpu2: cpu@100 {

		device_type = "cpu";

		compatible = "arm,cortex-a57";

		reg = <0x100>;

		enable-method = "psci";

		cpu-idle-states = <&CPU_SLEEP_0>;

		clocks = <&infracfg CLK_INFRA_CA57SEL>,

			 <&apmixedsys CLK_APMIXED_MAINPLL>;

		clock-names = "cpu", "intermediate";

	};



	cpu3: cpu@101 {

		device_type = "cpu";

		compatible = "arm,cortex-a57";

		reg = <0x101>;

		enable-method = "psci";

		cpu-idle-states = <&CPU_SLEEP_0>;

		clocks = <&infracfg CLK_INFRA_CA57SEL>,

			 <&apmixedsys CLK_APMIXED_MAINPLL>;

		clock-names = "cpu", "intermediate";

	};



	&cpu0 {

		proc-supply = <&mt6397_vpca15_reg>;

	};



	&cpu1 {

		proc-supply = <&mt6397_vpca15_reg>;

	};



	&cpu2 {

		proc-supply = <&da9211_vcpu_reg>;

		sram-supply = <&mt6397_vsramca7_reg>;

	};



	&cpu3 {

		proc-supply = <&da9211_vcpu_reg>;

		sram-supply = <&mt6397_vsramca7_reg>;

	};

Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt

+40 −3
Original line number Original line Diff line number Diff line
@@ -11,15 +11,14 @@ to various devfreq devices. The devfreq devices would use the event data when 
derterming the current state of each IP.

derterming the current state of each IP.





Required properties:

Required properties:

- compatible: Should be "samsung,exynos-ppmu".

- compatible: Should be "samsung,exynos-ppmu" or "samsung,exynos-ppmu-v2.

- reg: physical base address of each PPMU and length of memory mapped region.

- reg: physical base address of each PPMU and length of memory mapped region.





Optional properties:

Optional properties:

- clock-names : the name of clock used by the PPMU, "ppmu"

- clock-names : the name of clock used by the PPMU, "ppmu"

- clocks : phandles for clock specified in "clock-names" property

- clocks : phandles for clock specified in "clock-names" property

- #clock-cells: should be 1.





Example1 : PPMU nodes in exynos3250.dtsi are listed below.

Example1 : PPMUv1 nodes in exynos3250.dtsi are listed below.





		ppmu_dmc0: ppmu_dmc0@106a0000 {

		ppmu_dmc0: ppmu_dmc0@106a0000 {

			compatible = "samsung,exynos-ppmu";

			compatible = "samsung,exynos-ppmu";
@@ -108,3 +107,41 @@ Example2 : Events of each PPMU node in exynos3250-rinato.dts are listed below. 
			};

			};

		};

		};

	};

	};



Example3 : PPMUv2 nodes in exynos5433.dtsi are listed below.



		ppmu_d0_cpu: ppmu_d0_cpu@10480000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x10480000 0x2000>;

			status = "disabled";

		};



		ppmu_d0_general: ppmu_d0_general@10490000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x10490000 0x2000>;

			status = "disabled";

		};



		ppmu_d0_rt: ppmu_d0_rt@104a0000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x104a0000 0x2000>;

			status = "disabled";

		};



		ppmu_d1_cpu: ppmu_d1_cpu@104b0000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x104b0000 0x2000>;

			status = "disabled";

		};



		ppmu_d1_general: ppmu_d1_general@104c0000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x104c0000 0x2000>;

			status = "disabled";

		};



		ppmu_d1_rt: ppmu_d1_rt@104d0000 {

			compatible = "samsung,exynos-ppmu-v2";

			reg = <0x104d0000 0x2000>;

			status = "disabled";

		};

Documentation/devicetree/bindings/power/opp.txt→Documentation/devicetree/bindings/opp/opp.txt

+20 −20
Original line number Original line Diff line number Diff line
@@ -88,7 +88,7 @@ This defines voltage-current-frequency combinations along with other related 
properties.

properties.





Required properties:

Required properties:

- opp-hz: Frequency in Hz

- opp-hz: Frequency in Hz, expressed as a 64-bit big-endian integer.





Optional properties:

Optional properties:

- opp-microvolt: voltage in micro Volts.

- opp-microvolt: voltage in micro Volts.
@@ -158,20 +158,20 @@ Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together. 
		opp-shared;

		opp-shared;





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microamp = <70000>;

			opp-microamp = <70000>;

			clock-latency-ns = <300000>;

			clock-latency-ns = <300000>;

			opp-suspend;

			opp-suspend;

		};

		};

		opp01 {

		opp01 {

			opp-hz = <1100000000>;

			opp-hz = /bits/ 64 <1100000000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microamp = <80000>;

			opp-microamp = <80000>;

			clock-latency-ns = <310000>;

			clock-latency-ns = <310000>;

		};

		};

		opp02 {

		opp02 {

			opp-hz = <1200000000>;

			opp-hz = /bits/ 64 <1200000000>;

			opp-microvolt = <1025000>;

			opp-microvolt = <1025000>;

			clock-latency-ns = <290000>;

			clock-latency-ns = <290000>;

			turbo-mode;

			turbo-mode;
@@ -237,20 +237,20 @@ independently. 
		 */

		 */





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microamp = <70000>;

			opp-microamp = <70000>;

			clock-latency-ns = <300000>;

			clock-latency-ns = <300000>;

			opp-suspend;

			opp-suspend;

		};

		};

		opp01 {

		opp01 {

			opp-hz = <1100000000>;

			opp-hz = /bits/ 64 <1100000000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microamp = <80000>;

			opp-microamp = <80000>;

			clock-latency-ns = <310000>;

			clock-latency-ns = <310000>;

		};

		};

		opp02 {

		opp02 {

			opp-hz = <1200000000>;

			opp-hz = /bits/ 64 <1200000000>;

			opp-microvolt = <1025000>;

			opp-microvolt = <1025000>;

			opp-microamp = <90000;

			opp-microamp = <90000;

			lock-latency-ns = <290000>;

			lock-latency-ns = <290000>;
@@ -313,20 +313,20 @@ DVFS state together. 
		opp-shared;

		opp-shared;





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microvolt = <970000 975000 985000>;

			opp-microamp = <70000>;

			opp-microamp = <70000>;

			clock-latency-ns = <300000>;

			clock-latency-ns = <300000>;

			opp-suspend;

			opp-suspend;

		};

		};

		opp01 {

		opp01 {

			opp-hz = <1100000000>;

			opp-hz = /bits/ 64 <1100000000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microvolt = <980000 1000000 1010000>;

			opp-microamp = <80000>;

			opp-microamp = <80000>;

			clock-latency-ns = <310000>;

			clock-latency-ns = <310000>;

		};

		};

		opp02 {

		opp02 {

			opp-hz = <1200000000>;

			opp-hz = /bits/ 64 <1200000000>;

			opp-microvolt = <1025000>;

			opp-microvolt = <1025000>;

			opp-microamp = <90000>;

			opp-microamp = <90000>;

			clock-latency-ns = <290000>;

			clock-latency-ns = <290000>;
@@ -339,20 +339,20 @@ DVFS state together. 
		opp-shared;

		opp-shared;





		opp10 {

		opp10 {

			opp-hz = <1300000000>;

			opp-hz = /bits/ 64 <1300000000>;

			opp-microvolt = <1045000 1050000 1055000>;

			opp-microvolt = <1045000 1050000 1055000>;

			opp-microamp = <95000>;

			opp-microamp = <95000>;

			clock-latency-ns = <400000>;

			clock-latency-ns = <400000>;

			opp-suspend;

			opp-suspend;

		};

		};

		opp11 {

		opp11 {

			opp-hz = <1400000000>;

			opp-hz = /bits/ 64 <1400000000>;

			opp-microvolt = <1075000>;

			opp-microvolt = <1075000>;

			opp-microamp = <100000>;

			opp-microamp = <100000>;

			clock-latency-ns = <400000>;

			clock-latency-ns = <400000>;

		};

		};

		opp12 {

		opp12 {

			opp-hz = <1500000000>;

			opp-hz = /bits/ 64 <1500000000>;

			opp-microvolt = <1010000 1100000 1110000>;

			opp-microvolt = <1010000 1100000 1110000>;

			opp-microamp = <95000>;

			opp-microamp = <95000>;

			clock-latency-ns = <400000>;

			clock-latency-ns = <400000>;
@@ -379,7 +379,7 @@ Example 4: Handling multiple regulators 
		opp-shared;

		opp-shared;





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000>, /* Supply 0 */

			opp-microvolt = <970000>, /* Supply 0 */

					<960000>, /* Supply 1 */

					<960000>, /* Supply 1 */

					<960000>; /* Supply 2 */

					<960000>; /* Supply 2 */
@@ -392,7 +392,7 @@ Example 4: Handling multiple regulators 
		/* OR */

		/* OR */





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000 975000 985000>, /* Supply 0 */

			opp-microvolt = <970000 975000 985000>, /* Supply 0 */

					<960000 965000 975000>, /* Supply 1 */

					<960000 965000 975000>, /* Supply 1 */

					<960000 965000 975000>; /* Supply 2 */

					<960000 965000 975000>; /* Supply 2 */
@@ -405,7 +405,7 @@ Example 4: Handling multiple regulators 
		/* OR */

		/* OR */





		opp00 {

		opp00 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			opp-microvolt = <970000 975000 985000>, /* Supply 0 */

			opp-microvolt = <970000 975000 985000>, /* Supply 0 */

					<960000 965000 975000>, /* Supply 1 */

					<960000 965000 975000>, /* Supply 1 */

					<960000 965000 975000>; /* Supply 2 */

					<960000 965000 975000>; /* Supply 2 */
@@ -437,12 +437,12 @@ Example 5: Multiple OPP tables 
		opp-shared;

		opp-shared;





		opp00 {

		opp00 {

			opp-hz = <600000000>;

			opp-hz = /bits/ 64 <600000000>;

			...

			...

		};

		};





		opp01 {

		opp01 {

			opp-hz = <800000000>;

			opp-hz = /bits/ 64 <800000000>;

			...

			...

		};

		};

	};

	};
@@ -453,12 +453,12 @@ Example 5: Multiple OPP tables 
		opp-shared;

		opp-shared;





		opp10 {

		opp10 {

			opp-hz = <1000000000>;

			opp-hz = /bits/ 64 <1000000000>;

			...

			...

		};

		};





		opp11 {

		opp11 {

			opp-hz = <1100000000>;

			opp-hz = /bits/ 64 <1100000000>;

			...

			...

		};

		};

	};

	};