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

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

Pull power management updates from Rafael Wysocki:
 "These rework cpuidle governors to call tick_nohz_get_sleep_length()
  less often and fix one of them, rework hibernation to avoid storing
  pages filled with zeros in hibernation images, switch over some
  cpufreq drivers to use void remove callbacks, fix and clean up
  multiple cpufreq drivers, fix the devfreq core, update the cpupower
  utility and make other assorted improvements.

  Specifics:

   - Rework the menu and teo cpuidle governors to avoid calling
     tick_nohz_get_sleep_length(), which is likely to become quite
     expensive going forward, too often and improve making decisions
     regarding whether or not to stop the scheduler tick in the teo
     governor (Rafael Wysocki)

   - Improve the performance of cpufreq_stats_create_table() in some
     cases (Liao Chang)

   - Fix two issues in the amd-pstate-ut cpufreq driver (Swapnil Sapkal)

   - Use clamp() helper macro to improve the code readability in
     cpufreq_verify_within_limits() (Liao Chang)

   - Set stale CPU frequency to minimum in intel_pstate (Doug Smythies)

   - Migrate cpufreq drivers for various platforms to use void remove
     callback (Yangtao Li)

   - Add online/offline/exit hooks for Tegra driver (Sumit Gupta)

   - Explicitly include correct DT includes in cpufreq (Rob Herring)

   - Frequency domain updates for qcom-hw driver (Neil Armstrong)

   - Modify AMD pstate driver return the highest_perf value (Meng Li)

   - Generic cleanups for cppc, mediatek and powernow driver (Liao
     Chang, Konrad Dybcio)

   - Add more platforms to cpufreq-arm driver's blocklist
     (AngeloGioacchino Del Regno and Konrad Dybcio)

   - brcmstb-avs-cpufreq: Fix -Warray-bounds bug (Gustavo A. R. Silva)

   - Add device PM helpers to allow a device to remain powered-on during
     system-wide transitions (Ulf Hansson)

   - Rework hibernation memory snapshotting to avoid storing pages
     filled with zeros in hibernation image files (Brian Geffon)

   - Add check to make sure that CPU latency QoS constraints do not use
     negative values (Clive Lin)

   - Optimize rp->domains memory allocation in the Intel RAPL power
     capping driver (xiongxin)

   - Remove recursion while parsing zones in the arm_scmi power capping
     driver (Cristian Marussi)

   - Fix memory leak in devfreq_dev_release() (Boris Brezillon)

   - Rewrite devfreq_monitor_start() kerneldoc comment (Manivannan
     Sadhasivam)

   - Explicitly include correct DT includes in devfreq (Rob Herring)

   - Remove unsued pm_runtime_update_max_time_suspended() extern
     declaration (YueHaibing)

   - Add turbo-boost support to cpupower (Wyes Karny)

   - Add support for amd_pstate mode change to cpupower (Wyes Karny)

   - Fix 'cpupower idle_set' command to accept only numeric values of
     arguments (Likhitha Korrapati)

   - Clean up OPP code and add new frequency related APIs to it (Viresh
     Kumar, Manivannan Sadhasivam)

   - Convert ti cpufreq/opp bindings to json schema (Nishanth Menon)"

* tag 'pm-6.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (74 commits)
  cpufreq: tegra194: remove opp table in exit hook
  cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
  cpufreq: tegra194: add online/offline hooks
  cpuidle: teo: Avoid unnecessary variable assignments
  cpufreq: qcom-cpufreq-hw: add support for 4 freq domains
  dt-bindings: cpufreq: qcom-hw: add a 4th frequency domain
  cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
  cpufreq: amd-pstate-ut: Remove module parameter access
  cpufreq: Use clamp() helper macro to improve the code readability
  PM: sleep: Add helpers to allow a device to remain powered-on
  PM: QoS: Add check to make sure CPU latency is non-negative
  PM: runtime: Remove unsued extern declaration of pm_runtime_update_max_time_suspended()
  cpufreq: intel_pstate: set stale CPU frequency to minimum
  cpufreq: stats: Improve the performance of cpufreq_stats_create_table()
  dt-bindings: cpufreq: Convert ti-cpufreq to json schema
  dt-bindings: opp: Convert ti-omap5-opp-supply to json schema
  OPP: Fix argument name in doc comment
  cpuidle: menu: Skip tick_nohz_get_sleep_length() call in some cases
  cpufreq: cppc: Set fie_disabled to FIE_DISABLED if fails to create kworker_fie
  cpufreq: cppc: cppc_cpufreq_get_rate() returns zero in all error cases.
  ...
parents 330235e8 422ec6fe

Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml

+4 −1
Original line number Diff line number Diff line
@@ -49,6 +49,7 @@ properties: 
      - description: Frequency domain 0 register region

      - description: Frequency domain 1 register region

      - description: Frequency domain 2 register region

      - description: Frequency domain 3 register region



  reg-names:

    minItems: 1
@@ -56,6 +57,7 @@ properties: 
      - const: freq-domain0

      - const: freq-domain1

      - const: freq-domain2

      - const: freq-domain3



  clocks:

    items:
@@ -69,7 +71,7 @@ properties: 


  interrupts:

    minItems: 1

    maxItems: 3

    maxItems: 4



  interrupt-names:

    minItems: 1
@@ -77,6 +79,7 @@ properties: 
      - const: dcvsh-irq-0

      - const: dcvsh-irq-1

      - const: dcvsh-irq-2

      - const: dcvsh-irq-3



  '#freq-domain-cells':

    const: 1

Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt

deleted100644 → 0
+0 −132
Original line number Diff line number Diff line 
TI CPUFreq and OPP bindings

================================



Certain TI SoCs, like those in the am335x, am437x, am57xx, and dra7xx

families support different OPPs depending on the silicon variant in use.

The ti-cpufreq driver can use revision and an efuse value from the SoC to

provide the OPP framework with supported hardware information. This is

used to determine which OPPs from the operating-points-v2 table get enabled

when it is parsed by the OPP framework.



Required properties:

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

In 'cpus' nodes:

- operating-points-v2: Phandle to the operating-points-v2 table to use.



In 'operating-points-v2' table:

- compatible: Should be

	- 'operating-points-v2-ti-cpu' for am335x, am43xx, and dra7xx/am57xx,

	  omap34xx, omap36xx and am3517 SoCs

- syscon: A phandle pointing to a syscon node representing the control module

	  register space of the SoC.



Optional properties:

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

- "vdd-supply", "vbb-supply": to define two regulators for dra7xx

- "cpu0-supply", "vbb-supply": to define two regulators for omap36xx



For each opp entry in 'operating-points-v2' table:

- opp-supported-hw: Two bitfields indicating:

	1. Which revision of the SoC the OPP is supported by

	2. Which eFuse bits indicate this OPP is available



	A bitwise AND is performed against these values and if any bit

	matches, the OPP gets enabled.



Example:

--------



/* From arch/arm/boot/dts/am33xx.dtsi */

cpus {

	#address-cells = <1>;

	#size-cells = <0>;

	cpu@0 {

		compatible = "arm,cortex-a8";

		device_type = "cpu";

		reg = <0>;



		operating-points-v2 = <&cpu0_opp_table>;



		clocks = <&dpll_mpu_ck>;

		clock-names = "cpu";



		clock-latency = <300000>; /* From omap-cpufreq driver */

	};

};



/*

 * cpu0 has different OPPs depending on SoC revision and some on revisions

 * 0x2 and 0x4 have eFuse bits that indicate if they are available or not

 */

cpu0_opp_table: opp-table {

	compatible = "operating-points-v2-ti-cpu";

	syscon = <&scm_conf>;



	/*

	 * The three following nodes are marked with opp-suspend

	 * because they can not be enabled simultaneously on a

	 * single SoC.

	 */

	opp50-300000000 {

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

		opp-microvolt = <950000 931000 969000>;

		opp-supported-hw = <0x06 0x0010>;

		opp-suspend;

	};



	opp100-275000000 {

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

		opp-microvolt = <1100000 1078000 1122000>;

		opp-supported-hw = <0x01 0x00FF>;

		opp-suspend;

	};



	opp100-300000000 {

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

		opp-microvolt = <1100000 1078000 1122000>;

		opp-supported-hw = <0x06 0x0020>;

		opp-suspend;

	};



	opp100-500000000 {

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

		opp-microvolt = <1100000 1078000 1122000>;

		opp-supported-hw = <0x01 0xFFFF>;

	};



	opp100-600000000 {

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

		opp-microvolt = <1100000 1078000 1122000>;

		opp-supported-hw = <0x06 0x0040>;

	};



	opp120-600000000 {

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

		opp-microvolt = <1200000 1176000 1224000>;

		opp-supported-hw = <0x01 0xFFFF>;

	};



	opp120-720000000 {

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

		opp-microvolt = <1200000 1176000 1224000>;

		opp-supported-hw = <0x06 0x0080>;

	};



	oppturbo-720000000 {

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

		opp-microvolt = <1260000 1234800 1285200>;

		opp-supported-hw = <0x01 0xFFFF>;

	};



	oppturbo-800000000 {

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

		opp-microvolt = <1260000 1234800 1285200>;

		opp-supported-hw = <0x06 0x0100>;

	};



	oppnitro-1000000000 {

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

		opp-microvolt = <1325000 1298500 1351500>;

		opp-supported-hw = <0x04 0x0200>;

	};

};

Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml

0 → 100644
+92 −0
Original line number Diff line number Diff line 
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)

%YAML 1.2

---

$id: http://devicetree.org/schemas/opp/operating-points-v2-ti-cpu.yaml#

$schema: http://devicetree.org/meta-schemas/core.yaml#



title: TI CPU OPP (Operating Performance Points)



description:

  TI SoCs, like those in the AM335x, AM437x, AM57xx, AM62x, and DRA7xx

  families, the CPU frequencies subset and the voltage value of each

  OPP vary based on the silicon variant used. The data sheet sections

  corresponding to "Operating Performance Points" describe the frequency

  and voltage values based on device type and speed bin information

  blown in corresponding eFuse bits as referred to by the Technical

  Reference Manual.



  This document extends the operating-points-v2 binding by providing

  the hardware description for the scheme mentioned above.



maintainers:

  - Nishanth Menon <nm@ti.com>



allOf:

  - $ref: opp-v2-base.yaml#



properties:

  compatible:

    const: operating-points-v2-ti-cpu



  syscon:

    $ref: /schemas/types.yaml#/definitions/phandle

    description: |

      points to syscon node representing the control module

      register space of the SoC.



  opp-shared: true



patternProperties:

  '^opp(-?[0-9]+)*$':

    type: object

    additionalProperties: false



    properties:

      clock-latency-ns: true

      opp-hz: true

      opp-microvolt: true

      opp-supported-hw: true

      opp-suspend: true

      turbo-mode: true



    required:

      - opp-hz

      - opp-supported-hw



required:

  - compatible

  - syscon



additionalProperties: false



examples:

  - |

    opp-table {

        compatible = "operating-points-v2-ti-cpu";

        syscon = <&scm_conf>;



        opp-300000000 {

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

            opp-microvolt = <1100000 1078000 1122000>;

            opp-supported-hw = <0x06 0x0020>;

            opp-suspend;

        };



        opp-500000000 {

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

            opp-microvolt = <1100000 1078000 1122000>;

            opp-supported-hw = <0x01 0xFFFF>;

        };



        opp-600000000 {

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

            opp-microvolt = <1100000 1078000 1122000>;

            opp-supported-hw = <0x06 0x0040>;

        };



        opp-1000000000 {

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

            opp-microvolt = <1325000 1298500 1351500>;

            opp-supported-hw = <0x04 0x0200>;

        };

    };

Documentation/devicetree/bindings/opp/opp-v2-base.yaml

+1 −1
Original line number Diff line number Diff line
@@ -56,7 +56,7 @@ patternProperties: 
          need to be configured and that is left for the implementation

          specific binding.

        minItems: 1

        maxItems: 16

        maxItems: 32

        items:

          maxItems: 1

Documentation/devicetree/bindings/opp/ti,omap-opp-supply.yaml

0 → 100644
+101 −0
Original line number Diff line number Diff line 
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)

%YAML 1.2

---

$id: http://devicetree.org/schemas/opp/ti,omap-opp-supply.yaml#

$schema: http://devicetree.org/meta-schemas/core.yaml#



title: Texas Instruments OMAP compatible OPP supply



description:

  OMAP5, DRA7, and AM57 families of SoCs have Class 0 AVS eFuse

  registers, which contain OPP-specific voltage information tailored

  for the specific device. This binding provides the information

  needed to describe such a hardware values and relate them to program

  the primary regulator during an OPP transition.



  Also, some supplies may have an associated vbb-supply, an Adaptive

  Body Bias regulator, which must transition in a specific sequence

  w.r.t the vdd-supply and clk when making an OPP transition. By

  supplying two regulators to the device that will undergo OPP

  transitions, we can use the multi-regulator support implemented by

  the OPP core to describe both regulators the platform needs. The

  OPP core binding Documentation/devicetree/bindings/opp/opp-v2.yaml

  provides further information (refer to Example 4 Handling multiple

  regulators).



maintainers:

  - Nishanth Menon <nm@ti.com>



properties:

  $nodename:

    pattern: '^opp-supply(@[0-9a-f]+)?$'



  compatible:

    oneOf:

      - description: Basic OPP supply controlling VDD and VBB

        const: ti,omap-opp-supply

      - description: OMAP5+ optimized voltages in efuse(Class 0) VDD along with

          VBB.

        const: ti,omap5-opp-supply

      - description: OMAP5+ optimized voltages in efuse(class0) VDD but no VBB

        const: ti,omap5-core-opp-supply



  reg:

    maxItems: 1



  ti,absolute-max-voltage-uv:

    $ref: /schemas/types.yaml#/definitions/uint32

    description: Absolute maximum voltage for the OPP supply in micro-volts.

    minimum: 750000

    maximum: 1500000



  ti,efuse-settings:

    description: An array of u32 tuple items providing information about

      optimized efuse configuration.

    minItems: 1

    $ref: /schemas/types.yaml#/definitions/uint32-matrix

    items:

      items:

        - description: Reference voltage in micro-volts (OPP Voltage)

          minimum: 750000

          maximum: 1500000

          multipleOf: 10000

        - description: efuse offset where the optimized voltage is located

          multipleOf: 4

          maximum: 256



required:

  - compatible

  - ti,absolute-max-voltage-uv



allOf:

  - if:

      not:

        properties:

          compatible:

            contains:

              const: ti,omap-opp-supply

    then:

      required:

        - reg

        - ti,efuse-settings



additionalProperties: false



examples:

  - |

    opp-supply {

        compatible = "ti,omap-opp-supply";

        ti,absolute-max-voltage-uv = <1375000>;

    };

  - |

    opp-supply@4a003b20 {

        compatible = "ti,omap5-opp-supply";

        reg = <0x4a003b20 0x8>;

        ti,efuse-settings =

            /* uV   offset */

            <1060000 0x0>,

            <1160000 0x4>,

            <1210000 0x8>;

        ti,absolute-max-voltage-uv = <1500000>;

    };