From: Rob Herring <robh@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Niklas Cassel <nks@flawful.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Robert Marko <robimarko@gmail.com>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>
Subject: Re: [PATCH v14 3/9] dt-bindings: soc: qcom: cpr3: Add bindings for CPR3 driver
Date: Thu, 31 Aug 2023 11:28:35 -0500 [thread overview]
Message-ID: <20230831162835.GA2390385-robh@kernel.org> (raw)
In-Reply-To: <CAPDyKFrXT+2NEMUzVv-kWjXAhLinXq99GKq4_Ge2VjthtYxtaA@mail.gmail.com>
On Tue, Aug 29, 2023 at 01:01:44PM +0200, Ulf Hansson wrote:
> On Mon, 28 Aug 2023 at 13:42, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
> >
> > From: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
> >
> > Add the bindings for the CPR3 driver to the documentation.
> >
> > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
> > [Konrad: Make binding check pass; update AGdR's email]
> > Tested-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> > Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> > ---
> > .../devicetree/bindings/soc/qcom/qcom,cpr3.yaml | 286 +++++++++++++++++++++
> > 1 file changed, 286 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,cpr3.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,cpr3.yaml
> > new file mode 100644
> > index 000000000000..acf2e294866b
>
> [...]
>
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/clock/qcom,gcc-msm8998.h>
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > +
> > + cpus {
> > + #address-cells = <2>;
> > + #size-cells = <0>;
> > +
> > + cpu@0 {
> > + compatible = "qcom,kryo280";
> > + device_type = "cpu";
> > + reg = <0x0 0x0>;
> > + operating-points-v2 = <&cpu0_opp_table>;
> > + power-domains = <&apc_cprh 0>;
> > + power-domain-names = "cprh";
>
> Rather than using a Qcom specific power-domain-name, perhaps a common
> power-domain-name for cpus, that can be used for "the performance
> domain" would be a good idea here?
>
> I have suggested using "perf" for the SCMI performance domain [1],
> perhaps that description should be extended to cover this and other
> performance domains too?
Better yet, nothing. There's no value to -names when there is only 1
entry.
Rob
next prev parent reply other threads:[~2023-08-31 16:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 11:42 [PATCH v14 0/9] Add support for Core Power Reduction v3, v4 and Hardened Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 1/9] MAINTAINERS: Add entry for Qualcomm CPRv3/v4/Hardened driver Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 2/9] dt-bindings: opp: v2-qcom-level: Document CPR3 open/closed loop volt adjustment Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 3/9] dt-bindings: soc: qcom: cpr3: Add bindings for CPR3 driver Konrad Dybcio
2023-08-29 11:01 ` Ulf Hansson
2023-08-31 16:28 ` Rob Herring [this message]
2023-08-31 16:40 ` Konrad Dybcio
2023-08-31 22:02 ` Ulf Hansson
2023-09-09 12:00 ` Konrad Dybcio
2023-08-31 21:47 ` Ulf Hansson
2023-08-28 11:42 ` [PATCH v14 4/9] soc: qcom: cpr: Move common functions to new file Konrad Dybcio
2023-08-29 15:15 ` Bjorn Andersson
2023-09-09 11:59 ` Konrad Dybcio
2024-06-18 23:33 ` Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 5/9] soc: qcom: cpr-common: Add support for flat fuse adjustment Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 6/9] soc: qcom: cpr: Use u64 for frequency Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 7/9] soc: qcom: cpr-common: Add threads support Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 8/9] soc: qcom: Add support for Core Power Reduction v3, v4 and Hardened Konrad Dybcio
2023-09-06 10:23 ` Ulf Hansson
2024-06-19 20:07 ` Konrad Dybcio
2023-08-28 11:42 ` [PATCH v14 9/9] arm64: dts: qcom: msm8998: Configure CPRh Konrad Dybcio
2024-06-12 7:53 ` [PATCH v14 0/9] Add support for Core Power Reduction v3, v4 and Hardened Varadarajan Narayanan
2024-06-18 23:58 ` Konrad Dybcio
2024-06-19 7:09 ` Varadarajan Narayanan
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=20230831162835.GA2390385-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=nks@flawful.org \
--cc=nm@ti.com \
--cc=quic_jhugo@quicinc.com \
--cc=rafael@kernel.org \
--cc=robimarko@gmail.com \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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).