mirror of
https://github.com/hardkernel/linux.git
synced 2026-06-05 18:41:58 +09:00
UPSTREAM: dt-bindings: power: Clarify performance capabilities of power-domains
The power-domains bindings has in many years been used to describe so called performance-domains too. Rather than using a separate binding it has been convenient to re-use the power-domain bindings, as in some cases it's in fact a combination of the both that would be the best description. Therefore, let's make it more clear that the power-domains bindings can be used to describe a performance-domain too. Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: Kevin Hilman <khilman@kernel.org> Cc: Rob Herring <robh+dt@kernel.org> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: Conor Dooley <conor+dt@kernel.org> Cc: devicetree@vger.kernel.org Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Reviewed-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20230825112633.236607-11-ulf.hansson@linaro.org Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> Bug: 323966425 Change-Id: I46cc27dec351160f20a76d29d419ba8e0f161c1b (cherry picked from commit 0ead1f3e158c44aa274f2d5c49be947fbfcdffe0) Signed-off-by: Nikunj Kela <quic_nkela@quicinc.com> Signed-off-by: Anant Goel <quic_anantg@quicinc.com>
This commit is contained in:
@@ -13,8 +13,9 @@ maintainers:
|
|||||||
|
|
||||||
description: |+
|
description: |+
|
||||||
System on chip designs are often divided into multiple PM domains that can be
|
System on chip designs are often divided into multiple PM domains that can be
|
||||||
used for power gating of selected IP blocks for power saving by reduced leakage
|
used for power gating of selected IP blocks for power saving by reduced
|
||||||
current.
|
leakage current. Moreover, in some cases the similar PM domains may also be
|
||||||
|
capable of scaling performance for a group of IP blocks.
|
||||||
|
|
||||||
This device tree binding can be used to bind PM domain consumer devices with
|
This device tree binding can be used to bind PM domain consumer devices with
|
||||||
their PM domains provided by PM domain providers. A PM domain provider can be
|
their PM domains provided by PM domain providers. A PM domain provider can be
|
||||||
@@ -25,7 +26,7 @@ description: |+
|
|||||||
|
|
||||||
properties:
|
properties:
|
||||||
$nodename:
|
$nodename:
|
||||||
pattern: "^(power-controller|power-domain)([@-].*)?$"
|
pattern: "^(power-controller|power-domain|performance-domain)([@-].*)?$"
|
||||||
|
|
||||||
domain-idle-states:
|
domain-idle-states:
|
||||||
$ref: /schemas/types.yaml#/definitions/phandle-array
|
$ref: /schemas/types.yaml#/definitions/phandle-array
|
||||||
@@ -47,11 +48,11 @@ properties:
|
|||||||
items:
|
items:
|
||||||
maxItems: 1
|
maxItems: 1
|
||||||
description:
|
description:
|
||||||
Phandles to the OPP tables of power domains provided by a power domain
|
Phandles to the OPP tables of power domains that are capable of scaling
|
||||||
provider. If the provider provides a single power domain only or all
|
performance, provided by a power domain provider. If the provider provides
|
||||||
the power domains provided by the provider have identical OPP tables,
|
a single power domain only or all the power domains provided by the
|
||||||
then this shall contain a single phandle. Refer to ../opp/opp-v2-base.yaml
|
provider have identical OPP tables, then this shall contain a single
|
||||||
for more information.
|
phandle. Refer to ../opp/opp-v2-base.yaml for more information.
|
||||||
|
|
||||||
"#power-domain-cells":
|
"#power-domain-cells":
|
||||||
description:
|
description:
|
||||||
|
|||||||
Reference in New Issue
Block a user