-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'cpufreq/arm/linux-next' of git://git.kernel.org/pub/scm…
…/linux/kernel/git/vireshk/pm Pull ARM cpufreq updates for v5.14-rc1 from Viresh Kumar: "- Add frequency invariance support for CPPC driver again and related fixes/changes." - Minor changes/cleanups for Meditak driver (Fabien Parent and Seiya Wang), Qcom platform (Sibi Sankar), and SCMI driver (Christophe JAILLET). - New bindings for generic performance domains (Sudeep Holla). - Rename black/white-lists (Viresh Kumar)." * 'cpufreq/arm/linux-next' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm: cpufreq: CPPC: Add support for frequency invariance arch_topology: Avoid use-after-free for scale_freq_data cpufreq: CPPC: Pass structure instance by reference cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init dt-bindings: cpufreq: update cpu type and clock name for MT8173 SoC clk: mediatek: remove deprecated CLK_INFRA_CA57SEL for MT8173 SoC cpufreq: dt: Rename black/white-lists cpufreq: scmi: Fix an error message cpufreq: mediatek: add support for mt8365 dt-bindings: dvfs: Add support for generic performance domains cpufreq: blacklist SC7280 in cpufreq-dt-platdev
- Loading branch information
Showing
12 changed files
with
390 additions
and
42 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
74 changes: 74 additions & 0 deletions
74
Documentation/devicetree/bindings/dvfs/performance-domain.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,74 @@ | ||
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) | ||
%YAML 1.2 | ||
--- | ||
$id: http://devicetree.org/schemas/dvfs/performance-domain.yaml# | ||
$schema: http://devicetree.org/meta-schemas/core.yaml# | ||
|
||
title: Generic performance domains | ||
|
||
maintainers: | ||
- Sudeep Holla <sudeep.holla@arm.com> | ||
|
||
description: |+ | ||
This binding is intended for performance management of groups of devices or | ||
CPUs that run in the same performance domain. Performance domains must not | ||
be confused with power domains. A performance domain is defined by a set | ||
of devices that always have to run at the same performance level. For a given | ||
performance domain, there is a single point of control that affects all the | ||
devices in the domain, making it impossible to set the performance level of | ||
an individual device in the domain independently from other devices in | ||
that domain. For example, a set of CPUs that share a voltage domain, and | ||
have a common frequency control, is said to be in the same performance | ||
domain. | ||
This device tree binding can be used to bind performance domain consumer | ||
devices with their performance domains provided by performance domain | ||
providers. A performance domain provider can be represented by any node in | ||
the device tree and can provide one or more performance domains. A consumer | ||
node can refer to the provider by a phandle and a set of phandle arguments | ||
(so called performance domain specifiers) of length specified by the | ||
\#performance-domain-cells property in the performance domain provider node. | ||
select: true | ||
|
||
properties: | ||
"#performance-domain-cells": | ||
description: | ||
Number of cells in a performance domain specifier. Typically 0 for nodes | ||
representing a single performance domain and 1 for nodes providing | ||
multiple performance domains (e.g. performance controllers), but can be | ||
any value as specified by device tree binding documentation of particular | ||
provider. | ||
enum: [ 0, 1 ] | ||
|
||
performance-domains: | ||
$ref: '/schemas/types.yaml#/definitions/phandle-array' | ||
maxItems: 1 | ||
description: | ||
A phandle and performance domain specifier as defined by bindings of the | ||
performance controller/provider specified by phandle. | ||
|
||
additionalProperties: true | ||
|
||
examples: | ||
- | | ||
performance: performance-controller@12340000 { | ||
compatible = "qcom,cpufreq-hw"; | ||
reg = <0x12340000 0x1000>; | ||
#performance-domain-cells = <1>; | ||
}; | ||
// The node above defines a performance controller that is a performance | ||
// domain provider and expects one cell as its phandle argument. | ||
cpus { | ||
#address-cells = <2>; | ||
#size-cells = <0>; | ||
cpu@0 { | ||
device_type = "cpu"; | ||
compatible = "arm,cortex-a57"; | ||
reg = <0x0 0x0>; | ||
performance-domains = <&performance 1>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.