devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: cpufreq: qcom-hw: add a 4th frequency domain
Date: Wed, 23 Aug 2023 08:16:43 -0500	[thread overview]
Message-ID: <20230823131643.GA2164592-robh@kernel.org> (raw)
In-Reply-To: <20230821-topic-sm8x50-upstream-cpufreq-4-domains-v1-1-2d4d9fc828d8@linaro.org>

On Mon, Aug 21, 2023 at 09:39:13AM +0200, Neil Armstrong wrote:
> On new platforms, a 4th frequency domain is used, document it.
> 
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
>  Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> index a6b3bb8fdf33..c1d225fcf2d5 100644
> --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
> @@ -49,6 +49,7 @@ properties:
>        - description: Frequency domain 0 register region
>        - description: Frequency domain 1 register region
>        - description: Frequency domain 2 register region
> +      - description: Frequency domain 3 register region
>  
>    reg-names:
>      minItems: 1
> @@ -56,6 +57,7 @@ properties:
>        - const: freq-domain0
>        - const: freq-domain1
>        - const: freq-domain2
> +      - const: freq-domain3
>  
>    clocks:
>      items:
> @@ -69,7 +71,7 @@ properties:
>  
>    interrupts:
>      minItems: 1
> -    maxItems: 3
> +    maxItems: 4
>  
>    interrupt-names:
>      minItems: 1
> @@ -77,6 +79,7 @@ properties:
>        - const: dcvsh-irq-0
>        - const: dcvsh-irq-1
>        - const: dcvsh-irq-2
> +      - const: dcvsh-irq-3

Truly useless names with foo<index>...

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2023-08-23 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  7:39 [PATCH 0/2] qcom-cpufreq-hw: add support for 4 freq domains Neil Armstrong
2023-08-21  7:39 ` [PATCH 1/2] dt-bindings: cpufreq: qcom-hw: add a 4th frequency domain Neil Armstrong
2023-08-23  8:07   ` Manivannan Sadhasivam
2023-08-23 13:16   ` Rob Herring [this message]
2023-08-21  7:39 ` [PATCH 2/2] cpufreq: qcom-cpufreq-hw: add support for 4 freq domains Neil Armstrong
2023-08-21 11:48   ` Konrad Dybcio
2023-08-23 15:01 ` [PATCH 0/2] " Viresh Kumar

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=20230823131643.GA2164592-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rafael@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;
as well as URLs for NNTP newsgroup(s).