From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org
Cc: lukasz.luba@arm.com, dietmar.eggemann@arm.com,
viresh.kumar@linaro.org, rafael@kernel.org,
daniel.lezcano@linaro.org, nm@ti.com, sboyd@kernel.org,
mka@chromium.org, dianders@chromium.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [[PATCH v2 1/2] dt-bindings: opp: Add 'opp-microwatt' entry in the OPP
Date: Tue, 22 Feb 2022 14:07:45 +0000 [thread overview]
Message-ID: <20220222140746.12293-2-lukasz.luba@arm.com> (raw)
In-Reply-To: <20220222140746.12293-1-lukasz.luba@arm.com>
Add new entry for the OPP which provides information about power
expressed in micro-Watts. It is useful for the Energy Model framework.
Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
---
Documentation/devicetree/bindings/opp/opp-v2-base.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
index 15a76bcd6d42..3f07a279ed2a 100644
--- a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
+++ b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml
@@ -93,6 +93,13 @@ patternProperties:
minItems: 1
maxItems: 8 # Should be enough regulators
+ opp-microwatt:
+ description:
+ Power for the OPP
+
+ A value representing power for the OPP in micro-Watts.
+ $ref: /schemas/types.yaml#/definitions/uint32
+
opp-level:
description:
A value representing the performance level of the device.
--
2.17.1
next prev parent reply other threads:[~2022-02-22 14:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 14:07 [PATCH v2 0/2] Introduce 'advanced' Energy Model in DT Lukasz Luba
2022-02-22 14:07 ` Lukasz Luba [this message]
2022-02-23 5:50 ` [[PATCH v2 1/2] dt-bindings: opp: Add 'opp-microwatt' entry in the OPP Viresh Kumar
2022-02-23 8:39 ` Lukasz Luba
2022-02-23 8:45 ` Viresh Kumar
2022-02-22 14:07 ` [[PATCH v2 2/2] OPP: Add 'opp-microwatt' parsing for advanced EM registration Lukasz Luba
2022-02-22 14:58 ` Matthias Kaehlcke
2022-02-22 15:21 ` Lukasz Luba
2022-02-23 5:53 ` Viresh Kumar
2022-02-23 8:59 ` Lukasz Luba
2022-02-23 9:10 ` Viresh Kumar
2022-02-23 9:13 ` Lukasz Luba
2022-02-23 9:52 ` [PATCH v2 0/2] Introduce 'advanced' Energy Model in DT Daniel Lezcano
2022-02-23 10:16 ` Lukasz Luba
2022-02-23 10:43 ` Viresh Kumar
2022-02-23 11:22 ` Lukasz Luba
2022-02-23 11:27 ` Viresh Kumar
2022-02-23 11:40 ` Lukasz Luba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220222140746.12293-2-lukasz.luba@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox