From: Rob Herring <robh@kernel.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, 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,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 1/5] dt-bindings: opp: Add "opp-microwatt" entry in the OPP
Date: Wed, 2 Mar 2022 11:45:13 -0600 [thread overview]
Message-ID: <Yh+tKe7oWCpmj5MC@robh.at.kernel.org> (raw)
In-Reply-To: <20220302112917.27270-2-lukasz.luba@arm.com>
On Wed, Mar 02, 2022 at 11:29:13AM +0000, Lukasz Luba wrote:
> 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>
> ---
> .../devicetree/bindings/opp/opp-v2-base.yaml | 23 +++++++++++++++++++
> 1 file changed, 23 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-03-02 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 11:29 [PATCH v5 0/5] Introduce "opp-microwatt" and Energy Model from DT Lukasz Luba
2022-03-02 11:29 ` [PATCH v5 1/5] dt-bindings: opp: Add "opp-microwatt" entry in the OPP Lukasz Luba
2022-03-02 17:45 ` Rob Herring [this message]
2022-03-02 17:46 ` Lukasz Luba
2022-03-02 11:29 ` [PATCH v5 2/5] OPP: Add "opp-microwatt" supporting code Lukasz Luba
2022-03-02 11:29 ` [PATCH v5 3/5] PM: EM: add macro to set .active_power() callback conditionally Lukasz Luba
2022-03-02 11:29 ` [PATCH v5 4/5] OPP: Add support of "opp-microwatt" for EM registration Lukasz Luba
2022-03-02 11:29 ` [PATCH v5 5/5] Documentation: EM: Describe new registration method using DT Lukasz Luba
2022-03-03 4:05 ` [PATCH v5 0/5] Introduce "opp-microwatt" and Energy Model from DT Viresh Kumar
2022-03-03 6:57 ` 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=Yh+tKe7oWCpmj5MC@robh.at.kernel.org \
--to=robh@kernel.org \
--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=lukasz.luba@arm.com \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=rafael@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
all inboxes | Powered by JetHome®