From: Rob Herring <robh@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawn.guo@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/7] dt-bindings: interconnect: qcom: Introduce qcom,rpm-common
Date: Fri, 11 Aug 2023 10:48:14 -0600 [thread overview]
Message-ID: <20230811164814.GA3587580-robh@kernel.org> (raw)
In-Reply-To: <20230721-topic-icc_bindings-v2-1-e33d5acbf3bd@linaro.org>
On Mon, Jul 24, 2023 at 04:06:27PM +0200, Konrad Dybcio wrote:
> The current RPM interconnect bindings are messy. Start cleaning them
> up with a common include.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> .../bindings/interconnect/qcom,qcm2290.yaml | 18 +++++++-------
> .../bindings/interconnect/qcom,rpm-common.yaml | 28 ++++++++++++++++++++++
> 2 files changed, 36 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml b/Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml
> index f65a2fe846de..df89f390a9b0 100644
> --- a/Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml
> @@ -13,6 +13,9 @@ description: |
> The Qualcomm QCM2290 interconnect providers support adjusting the
> bandwidth requirements between the various NoC fabrics.
>
> +allOf:
> + - $ref: qcom,rpm-common.yaml#
> +
> properties:
> reg:
> maxItems: 1
> @@ -23,9 +26,6 @@ properties:
> - qcom,qcm2290-cnoc
> - qcom,qcm2290-snoc
>
> - '#interconnect-cells':
> - const: 1
> -
> clock-names:
> items:
> - const: bus
> @@ -44,6 +44,9 @@ patternProperties:
> The interconnect providers do not have a separate QoS register space,
> but share parent's space.
>
> + allOf:
> + - $ref: qcom,rpm-common.yaml#
> +
> properties:
> compatible:
> enum:
> @@ -51,9 +54,6 @@ patternProperties:
> - qcom,qcm2290-mmrt-virt
> - qcom,qcm2290-mmnrt-virt
>
> - '#interconnect-cells':
> - const: 1
> -
> clock-names:
> items:
> - const: bus
> @@ -66,20 +66,18 @@ patternProperties:
>
> required:
> - compatible
> - - '#interconnect-cells'
> - clock-names
> - clocks
>
> - additionalProperties: false
> + unevaluatedProperties: false
>
> required:
> - compatible
> - reg
> - - '#interconnect-cells'
> - clock-names
> - clocks
>
> -additionalProperties: false
> +unevaluatedProperties: false
>
> examples:
> - |
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,rpm-common.yaml b/Documentation/devicetree/bindings/interconnect/qcom,rpm-common.yaml
> new file mode 100644
> index 000000000000..1ea52b091609
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,rpm-common.yaml
> @@ -0,0 +1,28 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,rpm-common.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm RPMh Network-On-Chip Interconnect
> +
> +maintainers:
> + - Konrad Dybcio <konradybcio@kernel.org>
> +
> +description:
> + RPM interconnect providers support for managing system bandwidth requirements
> + through manual requests based on either predefined values or as indicated by
> + the bus monitor hardware. Each provider node represents a NoC bus master,
> + driven by a dedicated clock source.
> +
> +properties:
> + '#interconnect-cells':
> + oneOf:
> + - const: 2
> + - const: 1
> + deprecated: true
I think this is kind of questionable for a single property. Do you
plan to add more properties here? Also, if you add a new user of this
schema, then it's going to allow the deprecated case when it could just
start with 2 only.
Rob
next prev parent reply other threads:[~2023-08-11 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 14:06 [PATCH v2 0/7] Update RPM ICC bindings Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 1/7] dt-bindings: interconnect: qcom: Introduce qcom,rpm-common Konrad Dybcio
2023-08-11 16:48 ` Rob Herring [this message]
2023-09-29 15:23 ` Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 2/7] dt-bindings: interconnect: qcom: qcm2290: Remove RPM bus clocks Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 3/7] dt-bindings: interconnect: qcom: Fix and separate out SDM660 Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 4/7] dt-bindings: interconnect: qcom: Fix and separate out MSM8996 Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 5/7] dt-bindings: interconnect: qcom: Fix and separate out MSM8939 Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 6/7] dt-bindings: interconnect: qcom: rpm: Clean up the file Konrad Dybcio
2023-07-24 14:06 ` [PATCH v2 7/7] dt-bindings: interconnect: qcom: rpm: Clean up the example Konrad Dybcio
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=20230811164814.GA3587580-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=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=konradybcio@kernel.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=marijn.suijten@somainline.org \
--cc=shawn.guo@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).