From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ishu Brar <patches@brar.si>
Cc: djakov@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, konradybcio@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: interconnect: qcom: Add SM7250 RPMh NoC
Date: Wed, 28 Oct 2026 08:59:24 +0100 [thread overview]
Message-ID: <20261028-classic-sloppy-harrier-72dfcf@quoll> (raw)
In-Reply-To: <010601a17d6212dc-ed028a84-ea72-48e7-a4d8-fea315dc42cc-000000@ap-northeast-1.amazonses.com>
On Tue, Oct 27, 2026 at 12:42:21PM +0000, Ishu Brar wrote:
> Document the Network-On-Chip interconnect providers of the Qualcomm
> SM7250 SoC (Snapdragon 765/765G/768G), which are controlled through RPMh
> Bus Clock Managers, and add the header with the node and slave IDs.
>
> Signed-off-by: Ishu Brar <patches@brar.si>
> ---
> .../bindings/interconnect/qcom,sm7250-rpmh.yaml | 105 +++++++++++++++
> .../dt-bindings/interconnect/qcom,sm7250-rpmh.h | 148 +++++++++++++++++++++
> 2 files changed, 253 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,sm7250-rpmh.yaml b/Documentation/devicetree/bindings/interconnect/qcom,sm7250-rpmh.yaml
> new file mode 100644
> index 000000000000..1ae1ebfc27e3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,sm7250-rpmh.yaml
> @@ -0,0 +1,105 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,sm7250-rpmh.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm RPMh Network-On-Chip Interconnect on SM7250
> +
> +maintainers:
> + - Ishu Brar <patches@brar.si>
> +
> +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.
> +
> + See also: include/dt-bindings/interconnect/qcom,sm7250-rpmh.h
> +
> +allOf:
> + - $ref: qcom,rpmh-common.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,sm7250-aggre1-noc
> + then:
> + required:
> + - clocks
> + else:
> + properties:
> + clocks: false
Entire allOf goes to the end, before unevaluatedProperties.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,sm7250-aggre1-noc
> + - qcom,sm7250-aggre2-noc
> + - qcom,sm7250-config-noc
> + - qcom,sm7250-dc-noc
> + - qcom,sm7250-gem-noc
> + - qcom,sm7250-mmss-noc
> + - qcom,sm7250-npu-noc
> + - qcom,sm7250-system-noc
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: aggre UFS PHY AXI clock
> + - description: aggre USB3 PRIM AXI clock
> +
> +patternProperties:
> + '^interconnect-[0-9]+$':
We actually do not need to enforce -0: '^interconnect(-[0-9]+)?$'
> + type: object
> + description:
> + The interconnect providers do not have a separate QoS register space,
> + but share parent's space.
> +
> + allOf:
> + - $ref: qcom,rpmh-common.yaml#
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-28 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261027-icc-sm7250-v4-0-f9bdaa3c1c7b@brar.si>
2026-10-27 12:42 ` Ishu Brar
2026-10-27 18:38 ` Krzysztof Kozlowski
2026-10-28 4:44 ` Ishu Brar
2026-10-28 7:59 ` Krzysztof Kozlowski [this message]
2026-10-28 8:10 ` Krzysztof Kozlowski
2026-10-31 5:19 ` Ishu Brar
2026-10-27 12:42 ` [PATCH v4 2/2] interconnect: qcom: Add SM7250 interconnect provider driver Ishu Brar
2026-10-27 13:04 ` Konrad Dybcio
2026-10-31 21:48 ` Dmitry Baryshkov
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=20261028-classic-sloppy-harrier-72dfcf@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@brar.si \
--cc=robh@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
all inboxes | Powered by JetHome®