From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rohit Agarwal <quic_rohiagar@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, djakov@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@quicinc.com
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: Add compatibles for SDX75
Date: Tue, 5 Sep 2023 08:59:39 +0200 [thread overview]
Message-ID: <c19e0ecf-7e8c-b9c3-0741-40c7aa3cb200@linaro.org> (raw)
In-Reply-To: <1693889975-19122-2-git-send-email-quic_rohiagar@quicinc.com>
On 05/09/2023 06:59, Rohit Agarwal wrote:
> Add dt-bindings compatibles and interconnect IDs for
> Qualcomm SDX75 platform.
>
> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
> ---
> .../bindings/interconnect/qcom,sdx75-rpmh.yaml | 100 ++++++++++++++++++++
> include/dt-bindings/interconnect/qcom,sdx75.h | 102 +++++++++++++++++++++
> 2 files changed, 202 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sdx75-rpmh.yaml
> create mode 100644 include/dt-bindings/interconnect/qcom,sdx75.h
>
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,sdx75-rpmh.yaml b/Documentation/devicetree/bindings/interconnect/qcom,sdx75-rpmh.yaml
> new file mode 100644
> index 0000000..f2dc87c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,sdx75-rpmh.yaml
> @@ -0,0 +1,100 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,sdx75-rpmh.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm RPMh Network-On-Chip Interconnect on SDX75
> +
> +maintainers:
> + - Georgi Djakov <djakov@kernel.org>
I don't think Georgi maintains this device. It's maintainer of device,
not the subsystem.
> +
> +description:
> + RPMh interconnect providers support system bandwidth requirements through
> + RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
> + able to communicate with the BCM through the Resource State Coordinator (RSC)
> + associated with each execution environment. Provider nodes must point to at
> + least one RPMh device child node pertaining to their RSC and each provider
> + can map to multiple RPMh resources.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,sdx75-clk-virt
> + - qcom,sdx75-dc-noc
> + - qcom,sdx75-gem-noc
> + - qcom,sdx75-mc-virt
> + - qcom,sdx75-pcie-anoc
> + - qcom,sdx75-system-noc
> +
> + '#interconnect-cells': true'
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> +allOf:
> + - $ref: qcom,rpmh-common.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sdx75-clk-virt
> + - qcom,sdx75-mc-virt
> + then:
> + properties:
> + reg: false
> + else:
> + required:
> + - reg
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sdx75-clk-virt
> + then:
> + properties:
> + clocks:
> + items:
> + - description: RPMH CC QPIC Clock
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sdx75-clk-virt
This if: clause should be merged with the one earlier.
> + then:
> + required:
> + - clocks
> + else:
> + properties:
> + clocks: false
> +
> +required:
> + - compatible
Please keep the order like in example-schema, so required: goes before
allOf.
> +
> +unevaluatedProperties: false
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-05 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 4:59 [PATCH 0/2] Add interconnect driver for SDX75 Rohit Agarwal
2023-09-05 4:59 ` [PATCH 1/2] dt-bindings: interconnect: Add compatibles " Rohit Agarwal
2023-09-05 6:59 ` Krzysztof Kozlowski [this message]
2023-09-05 7:14 ` Rohit Agarwal
2023-09-05 4:59 ` [PATCH 2/2] interconnect: qcom: Add SDX75 interconnect provider driver Rohit Agarwal
2023-09-05 7:02 ` Krzysztof Kozlowski
2023-09-05 7:20 ` Rohit Agarwal
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=c19e0ecf-7e8c-b9c3-0741-40c7aa3cb200@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=kernel@quicinc.com \
--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=quic_rohiagar@quicinc.com \
--cc=robh+dt@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