From: David Collins <collinsd@codeaurora.org>
To: Rajendra Nayak <rnayak@codeaurora.org>,
viresh.kumar@linaro.org, sboyd@kernel.org, andy.gross@linaro.org,
ulf.hansson@linaro.org
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] dt-bindings: opp: Introduce qcom-opp bindings
Date: Fri, 25 May 2018 15:33:43 -0700 [thread overview]
Message-ID: <67054dca-33a8-7e7c-6218-dc5abf84f6d8@codeaurora.org> (raw)
In-Reply-To: <20180525100121.28214-3-rnayak@codeaurora.org>
Hello Rajendra,
On 05/25/2018 03:01 AM, Rajendra Nayak wrote:
> On Qualcomm platforms, an OPP node needs to describe an
s/Qualcomm/Qualcomm Technologies, Inc./
> additional level/corner value that is then communicated to
> a remote microprocessor by the CPU, which then takes some
> actions (like adjusting voltage values across various rails)
> based on the value passed.
>
> Describe these bindings in the qcom-opp bindings document.
>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/opp/qcom-opp.txt | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/opp/qcom-opp.txt
>
> diff --git a/Documentation/devicetree/bindings/opp/qcom-opp.txt b/Documentation/devicetree/bindings/opp/qcom-opp.txt
> new file mode 100644
> index 000000000000..db4d970c7ec7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/opp/qcom-opp.txt
> @@ -0,0 +1,25 @@
> +Qualcomm OPP bindings to descibe OPP nodes with corner/level values
s/Qualcomm/Qualcomm Technologies, Inc./ ?
s/descibe/describe/
> +
> +OPP tables for devices on Qualcomm platforms require an additional
s/Qualcomm/Qualcomm Technologies, Inc./
> +platform specific corner/level value to be specified.
> +This value is passed on to the RPM (Resource Power Manager) by
Do you want to mention RPMh here as well?
> +the CPU, which then takes the necessary actions to set a voltage
> +rail to an appropriate voltage based on the value passed.
> +
> +The bindings are based on top of the operating-points-v2 bindings
> +described in Documentation/devicetree/bindings/opp/opp.txt
> +Additional properties are described below.
> +
> +* OPP Table Node
> +
> +Required properties:
> +- compatible: Allow OPPs to express their compatibility. It should be:
> + "operating-points-v2-qcom-level"
> +
> +* OPP Node
> +
> +Required properties:
> +- qcom,level: On Qualcomm platforms an OPP node can describe a positive value
s/Qualcomm/Qualcomm Technologies, Inc./
> +representing a corner/level that's communicated with a remote microprocessor
> +(usually called the RPM) which then translates it into a certain voltage on
> +a voltage rail.
Should these lines be indented 2 spaces as is the case for the compatible
property above?
Could you add an example for both RPM and RPMh in this binding file?
Thanks,
David
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-05-25 22:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 10:01 [PATCH v2 0/6] Add powerdomain driver for corners on msm8996/sdm845 Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 1/6] soc: qcom: rpmpd: Add a powerdomain driver to model corners Rajendra Nayak
2018-05-30 9:17 ` Ulf Hansson
2018-05-30 10:14 ` Rajendra Nayak
2018-05-30 12:44 ` Ulf Hansson
2018-05-31 4:20 ` Rajendra Nayak
2018-05-31 11:09 ` Ulf Hansson
2018-05-30 18:27 ` David Collins
2018-05-31 3:53 ` Rajendra Nayak
2018-05-31 3:27 ` Rob Herring
2018-05-31 4:14 ` Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 2/6] dt-bindings: opp: Introduce qcom-opp bindings Rajendra Nayak
2018-05-25 22:33 ` David Collins [this message]
2018-05-29 9:49 ` Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 3/6] soc: qcom: rpmpd: Add support for get/set performance state Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 4/6] arm64: dts: msm8996: Add rpmpd device node Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 5/6] soc: qcom: rpmh powerdomain driver Rajendra Nayak
2018-05-26 1:08 ` David Collins
2018-05-29 10:19 ` Rajendra Nayak
2018-05-29 19:03 ` David Collins
2018-05-30 8:55 ` Rajendra Nayak
2018-05-30 9:44 ` Viresh Kumar
2018-05-30 10:07 ` Rajendra Nayak
2018-06-01 8:48 ` Rajendra Nayak
2018-06-01 19:19 ` David Collins
2018-06-13 18:29 ` Lina Iyer
2018-05-31 3:31 ` Rob Herring
2018-05-31 4:15 ` Rajendra Nayak
2018-05-25 10:01 ` [PATCH v2 6/6] soc: qcom: rpmpd/rpmhpd: Add a max vote on all corners at init Rajendra Nayak
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=67054dca-33a8-7e7c-6218-dc5abf84f6d8@codeaurora.org \
--to=collinsd@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).