From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: bjorn.andersson@linaro.org, viresh.kumar@linaro.org,
agross@kernel.org, rjw@rjwysocki.net, devicetree@vger.kernel.org,
amit.kucheria@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
martin.botka@somainline.org, jami.kettunen@somainline.org,
paul.bouchara@somainline.org,
~postmarketos/upstreaming@lists.sr.ht, jeffrey.l.hugo@gmail.com
Subject: Re: [PATCH v6 8/9] dt-bindings: cpufreq: qcom-hw: Add bindings for 8998
Date: Wed, 14 Jul 2021 15:39:46 -0600 [thread overview]
Message-ID: <20210714213946.GA3568065@robh.at.kernel.org> (raw)
In-Reply-To: <20210701105730.322718-9-angelogioacchino.delregno@somainline.org>
On Thu, Jul 01, 2021 at 12:57:29PM +0200, AngeloGioacchino Del Regno wrote:
> The OSM programming addition has been done under the
> qcom,cpufreq-hw-8998 compatible name: specify the requirement
> of two additional register spaces for this functionality.
> This implementation, with the same compatible, has been
> tested on MSM8998 and SDM630.
Certainly we should be using the new binding for any new SoCs.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
> ---
> .../bindings/cpufreq/cpufreq-qcom-hw.yaml | 67 ++++++++++++++-----
> 1 file changed, 52 insertions(+), 15 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> index bc81b6203e27..29b663321a0b 100644
> --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> @@ -18,6 +18,10 @@ description: |
> properties:
> compatible:
> oneOf:
> + - description: Non-secure v1 of CPUFREQ HW
> + items:
> + - const: qcom,cpufreq-hw-8998
> +
> - description: v1 of CPUFREQ HW
> items:
> - const: qcom,cpufreq-hw
> @@ -28,21 +32,9 @@ properties:
> - qcom,sm8250-cpufreq-epss
> - const: qcom,cpufreq-epss
>
> - reg:
> - minItems: 2
> - maxItems: 3
> - items:
> - - description: Frequency domain 0 register region
> - - description: Frequency domain 1 register region
> - - description: Frequency domain 2 register region
> + reg: {}
>
> - reg-names:
> - minItems: 2
> - maxItems: 3
> - items:
> - - const: freq-domain0
> - - const: freq-domain1
> - - const: freq-domain2
> + reg-names: {}
>
> clocks:
> items:
> @@ -57,10 +49,55 @@ properties:
> '#freq-domain-cells':
> const: 1
>
> +if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,cpufreq-hw-8998
> +then:
> + properties:
> + reg:
> + minItems: 2
> + maxItems: 6
> + items:
> + - description: Frequency domain 0 register region
> + - description: Operating State Manager domain 0 register region
> + - description: Frequency domain 1 register region
> + - description: Operating State Manager domain 1 register region
> + - description: PLL ACD domain 0 register region (if ACD programming required)
> + - description: PLL ACD domain 1 register region (if ACD programming required)
> +
> + reg-names:
> + minItems: 2
> + maxItems: 6
> + items:
> + - const: "osm-domain0"
> + - const: "freq-domain0"
> + - const: "osm-domain1"
> + - const: "freq-domain1"
> + - const: "osm-acd0"
> + - const: "osm-acd1"
This is different enough and there's not much else to this bindings, so
I think you should do a separate schema doc.
BTW, Don't need quotes here.
> +
> +else:
> + properties:
> + reg:
> + minItems: 2
> + maxItems: 3
> + items:
> + - description: Frequency domain 0 register region
> + - description: Frequency domain 1 register region
> + - description: Frequency domain 2 register region
> + reg-names:
> + minItems: 2
> + maxItems: 3
> + items:
> + - const: "freq-domain0"
> + - const: "freq-domain1"
> + - const: "freq-domain2"
> +
> required:
> - compatible
> - reg
> - - reg-names
> - clocks
> - clock-names
> - '#freq-domain-cells'
> --
> 2.32.0
>
>
next prev parent reply other threads:[~2021-07-14 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 10:57 [PATCH v6 0/9] cpufreq-qcom-hw: Implement full OSM programming AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 1/9] cpufreq: blacklist SDM630/636/660 in cpufreq-dt-platdev AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 2/9] cpufreq: blacklist MSM8998 " AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 3/9] dt-bindings: arm: cpus: Document 'qcom,freq-domain' property AngeloGioacchino Del Regno
2021-07-08 8:37 ` Viresh Kumar
2021-07-01 10:57 ` [PATCH v6 4/9] dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings AngeloGioacchino Del Regno
2021-07-14 21:34 ` Rob Herring
2021-07-01 10:57 ` [PATCH v6 5/9] cpufreq: qcom-hw: Add kerneldoc to some functions AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 6/9] cpufreq: qcom-hw: Implement CPRh aware OSM programming AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 7/9] cpufreq: qcom-hw: Allow getting the maximum transition latency for OPPs AngeloGioacchino Del Regno
2021-07-08 8:41 ` Viresh Kumar
2021-07-01 10:57 ` [PATCH v6 8/9] dt-bindings: cpufreq: qcom-hw: Add bindings for 8998 AngeloGioacchino Del Regno
2021-07-14 21:39 ` Rob Herring [this message]
2021-07-21 10:48 ` AngeloGioacchino Del Regno
2021-07-01 10:57 ` [PATCH v6 9/9] dt-bindings: cpufreq: qcom-hw: Make reg-names a required property AngeloGioacchino Del Regno
2021-07-13 22:42 ` Rob Herring
2021-07-29 13:28 ` AngeloGioacchino Del Regno
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=20210714213946.GA3568065@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jami.kettunen@somainline.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=paul.bouchara@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).