| /linux/Documentation/devicetree/bindings/dvfs/ |
| H A D | performance-domain.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic performance domains 10 - Sudeep Holla <sudeep.holla@arm.com> 13 This binding is intended for performance management of groups of devices or 14 CPUs that run in the same performance domain. Performance domains must not 15 be confused with power domains. A performance domain is defined by a set 16 of devices that always have to run at the same performance level. For a given [all …]
|
| /linux/arch/arm64/boot/dts/apple/ |
| H A D | t6002.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ OR MIT 10 #include <dt-bindings/gpio/gpio.h> 11 #include <dt-bindings/interrupt-controller/apple-aic.h> 12 #include <dt-bindings/interrupt-controller/irq.h> 13 #include <dt-bindings/pinctrl/apple.h> 14 #include <dt-bindings/spmi/spmi.h> 16 #include "multi-die-cpp.h" 18 #include "t600x-common.dtsi" 21 compatible = "apple,t6002", "apple,arm-platform"; 23 #address-cells = <2>; [all …]
|
| H A D | t600x-common.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ OR MIT 11 #address-cells = <2>; 12 #size-cells = <2>; 19 #address-cells = <2>; 20 #size-cells = <0>; 22 cpu-map { 67 enable-method = "spin-table"; 68 cpu-release-addr = <0 0>; /* To be filled by loader */ 69 next-level-cache = <&l2_cache_0>; 70 i-cache-size = <0x20000>; [all …]
|
| H A D | t600x-dieX.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ OR MIT 10 …compatible = "apple,t6000-cluster-cpufreq", "apple,t8103-cluster-cpufreq", "apple,cluster-cpufreq"; 12 #performance-domain-cells = <0>; 16 …compatible = "apple,t6000-cluster-cpufreq", "apple,t8103-cluster-cpufreq", "apple,cluster-cpufreq"; 18 #performance-domain-cells = <0>; 22 …compatible = "apple,t6000-cluster-cpufreq", "apple,t8103-cluster-cpufreq", "apple,cluster-cpufreq"; 24 #performance-domain-cells = <0>; 27 DIE_NODE(pmgr): power-management@28e080000 { 28 compatible = "apple,t6000-pmgr", "apple,pmgr", "syscon", "simple-mfd"; 29 #address-cells = <1>; [all …]
|
| /linux/Documentation/scheduler/ |
| H A D | sched-energy.rst | 6 --------------- 25 please refer to its documentation (see Documentation/power/energy-model.rst). 29 ----------------------------- 32 - energy = [joule] (resource like a battery on powered devices) 33 - power = energy/time = [joule/second] = [watt] 38 performance [inst/s] 39 -------------------- 45 ----------- 48 while still getting 'good' performance. It is essentially an alternative 49 optimization objective to the current performance-only objective for the [all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | associativity.rst | 6 domains of substantially similar mean performance relative to resources outside 8 performance relative to each other than relative to other resources subsets 9 are represented as being members of a sub-grouping domain. This performance 11 From the platform view, these groups are also referred to as domains. 17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property". 18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1. 20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used. 23 ------ 27 ------ 28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity [all …]
|
| /linux/drivers/pmdomain/qcom/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 2 menu "Qualcomm PM Domains" 18 be called qcom-cpr 24 QCOM RPMh Power domain driver to support power-domains with 25 performance states. The driver communicates a performance state 36 QCOM RPM Power domain driver to support power-domains with 37 performance states. The driver communicates a performance state
|
| /linux/Documentation/devicetree/bindings/power/ |
| H A D | power-domain.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/power/power-domain.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic PM domains 10 - Rafael J. Wysocki <rafael@kernel.org> 11 - Kevin Hilman <khilman@kernel.org> 12 - Ulf Hansson <ulf.hansson@linaro.org> 15 System on chip designs are often divided into multiple PM domains that can be 17 leakage current. Moreover, in some cases the similar PM domains may also be [all …]
|
| /linux/drivers/pmdomain/arm/ |
| H A D | scmi_perf_domain.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * SCMI performance domain support. 32 if (!pd->info->set_perf) in scmi_pd_set_perf_state() 36 return -EINVAL; in scmi_pd_set_perf_state() 38 ret = pd->perf_ops->level_set(pd->ph, pd->domain_id, state, false); in scmi_pd_set_perf_state() 40 dev_warn(&genpd->dev, "Failed with %d when trying to set %d perf level", in scmi_pd_set_perf_state() 54 * the performance level can be changed. in scmi_pd_attach_dev() 56 if (!pd->info->set_perf) in scmi_pd_attach_dev() 59 ret = pd->perf_ops->device_opps_add(pd->ph, dev, pd->domain_id); in scmi_pd_attach_dev() 71 if (!pd->info->set_perf) in scmi_pd_detach_dev() [all …]
|
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 3 tristate "SCMI performance domain driver" 8 This enables support for the SCMI performance domains which can be 20 This enables support for the SCMI power domains which can be 33 This enables support for the SCPI power domains which can be
|
| /linux/drivers/base/power/ |
| H A D | common.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * drivers/base/power/common.c - Common device power management code. 19 * dev_pm_get_subsys_data - Create or refcount power.subsys_data for device. 32 return -ENOMEM; in dev_pm_get_subsys_data() 34 spin_lock_irq(&dev->power.lock); in dev_pm_get_subsys_data() 36 if (dev->power.subsys_data) { in dev_pm_get_subsys_data() 37 dev->power.subsys_data->refcount++; in dev_pm_get_subsys_data() 39 spin_lock_init(&psd->lock); in dev_pm_get_subsys_data() 40 psd->refcount = 1; in dev_pm_get_subsys_data() 41 dev->power.subsys_data = psd; in dev_pm_get_subsys_data() [all …]
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | cpufreq-mediatek-hw.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/cpufreq/cpufreq-mediatek-hw.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Hector Yuan <hector.yuan@mediatek.com> 19 const: mediatek,cpufreq-hw 29 "#performance-domain-cells": 31 Number of cells in a performance domain specifier. 33 performance domains. 37 - compatible [all …]
|
| /linux/Documentation/power/ |
| H A D | energy-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 ----------- 11 the power consumed by devices at various performance levels, and the kernel 12 subsystems willing to use that information to make energy-aware decisions. 18 each and every client subsystem to re-implement support for each and every 23 The power values might be expressed in micro-Watts or in an 'abstract scale'. 26 can be found in the Energy-Aware Scheduler documentation 27 Documentation/scheduler/sched-energy.rst. For some subsystems like thermal or 30 thus the real micro-Watts might be needed. An example of these requirements can 32 Documentation/driver-api/thermal/power_allocator.rst. [all …]
|
| H A D | opp.rst | 2 Operating Performance Points (OPP) Library 5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated 19 1.1 What is an Operating Performance Point (OPP)? 20 ------------------------------------------------- 22 Complex SoCs of today consists of a multiple sub-modules working in conjunction. 25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some 26 domains to run at lower voltage and frequency while other domains run at 30 the device will support per domain are called Operating Performance Points or 41 - {300000000, 1000000} 42 - {800000000, 1200000} [all …]
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 :Copyright: |copy| 2022-2023 Intel Corporation 13 ------------ 17 performance, SoCs have internal algorithms for scaling uncore frequency. These 20 It is possible that users have different expectations of uncore performance and 22 the scaling min/max frequencies via cpufreq sysfs to improve CPU performance. 25 different core and uncore performance at distinct phases and they may want to 27 improve overall performance. 30 --------------- 45 This is a read-only attribute. If users adjust max_freq_khz, [all …]
|
| /linux/arch/arm64/boot/dts/mediatek/ |
| H A D | mt8192.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT) 7 /dts-v1/; 8 #include <dt-bindings/clock/mt8192-clk.h> 9 #include <dt-bindings/gce/mt8192-gce.h> 10 #include <dt-bindings/interrupt-controller/arm-gic.h> 11 #include <dt-bindings/interrupt-controller/irq.h> 12 #include <dt-bindings/memory/mt8192-larb-port.h> 13 #include <dt-bindings/pinctrl/mt8192-pinfunc.h> 14 #include <dt-bindings/phy/phy.h> 15 #include <dt-bindings/power/mt8192-power.h> [all …]
|
| /linux/Documentation/driver-api/cxl/platform/acpi/ |
| H A D | srat.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 SRAT - Static Resource Affinity Table 8 affinity to "Proximity Domains". This table is technically optional, but for 9 performance information (see "HMAT") to be enumerated by linux it must be 13 created. If things don't look quite the way you expect - check the SRAT Memory 18 proximity domains. See linux numa creation for more information about how 23 A proximity domain is ROUGHLY equivalent to "NUMA Node" - though a 1-to-1 30 programming in BIOS - an SRAT entry for that memory needs to be present. 36 Proximity Domain : 00000001 <- NUMA Node 1 38 Base Address : 000000C050000000 <- Physical Memory Region [all …]
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | qcom,sm8350-videocc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/clock/qcom,sm8350-videocc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Konrad Dybcio <konradybcio@kernel.org> 14 domains on Qualcomm SoCs. 17 include/dt-bindings/clock/qcom,videocc-sm8350.h 18 include/dt-bindings/reset/qcom,videocc-sm8350.h 23 - qcom,sc8280xp-videocc 24 - qcom,sm8350-videocc [all …]
|
| H A D | qcom,sc8180x-camcc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/clock/qcom,sc8180x-camcc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Satya Priya Kakitapalli <quic_skakitap@quicinc.com> 14 power domains on SC8180X. 16 See also: include/dt-bindings/clock/qcom,sc8180x-camcc.h 20 const: qcom,sc8180x-camcc 24 - description: Camera AHB clock from GCC 25 - description: Board XO source [all …]
|
| H A D | qcom,qcm2290-gpucc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/clock/qcom,qcm2290-gpucc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Konrad Dybcio <konradybcio@kernel.org> 14 domains on Qualcomm SoCs. 17 include/dt-bindings/clock/qcom,qcm2290-gpucc.h 21 const: qcom,qcm2290-gpucc 28 - description: AHB interface clock, 29 - description: SoC CXO clock [all …]
|
| H A D | qcom,glymur-dispcc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/clock/qcom,glymur-dispcc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Taniya Das <taniya.das@oss.qualcomm.com> 14 power domains for the MDSS instances on GLYMUR SoC. 17 include/dt-bindings/clock/qcom,dispcc-glymur.h 22 - qcom,glymur-dispcc 26 - description: Board CXO clock 27 - description: Board sleep clock [all …]
|
| H A D | qcom,dispcc-sm8x50.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/clock/qcom,dispcc-sm8x50.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jonathan Marek <jonathan@marek.ca> 14 domains on SM8150/SM8250/SM8350. 17 include/dt-bindings/clock/qcom,dispcc-sm8150.h 18 include/dt-bindings/clock/qcom,dispcc-sm8250.h 19 include/dt-bindings/clock/qcom,dispcc-sm8350.h 24 - qcom,sc8180x-dispcc [all …]
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | nxp,dw100.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Xavier Roumegue <xavier.roumegue@oss.nxp.com> 12 description: |- 13 The Dewarp Engine provides high-performance dewarp processing for the 15 and wide angle lenses. It is implemented with a line/tile-cache based 24 - nxp,imx8mp-dw100 34 - description: The AXI clock 35 - description: The AHB clock [all …]
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | early-boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 Linux configuration is split into two major steps: Early-Boot and everything else. 23 There are 4 pre-boot options that need to be considered during kernel build 30 drivers to manage - and not immediately exposed as system RAM. 56 :code:`nosoftreserve=y` - Linux will default a CXL device memory region to 68 significant impact performance depending on the memory capacity of the system. 74 Linux refers to the proximity domains (:code:`PXM`) defined in the :doc:`SRAT 78 The SRAT is the only ACPI defined way of defining Proximity Domains. Linux 94 See :doc:`Example Platform Configurations <../platform/example-configs>` 99 Memory tiers are a collection of NUMA nodes grouped by performance characteristics. [all …]
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | qcom,msm8996.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm MSM8996 Network-On-Chip interconnect 10 - Konrad Dybcio <konradybcio@kernel.org> 19 - qcom,msm8996-a0noc 20 - qcom,msm8996-a1noc 21 - qcom,msm8996-a2noc 22 - qcom,msm8996-bimc 23 - qcom,msm8996-cnoc [all …]
|