From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
Cc: Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: document the RPM Network-On-Chip interconnect in Shikra SoC
Date: Sun, 3 May 2026 18:17:22 +0200 [thread overview]
Message-ID: <20260503-enormous-benign-salamander-8d074c@quoll> (raw)
In-Reply-To: <20260429-shikra_icc-v1-1-e3439903edf1@oss.qualcomm.com>
On Wed, Apr 29, 2026 at 02:03:48PM +0000, Raviteja Laggyshetty wrote:
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,shikra.yaml
> @@ -0,0 +1,135 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,shikra.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Shikra Network-On-Chip interconnect
> +
> +maintainers:
> + - Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + The Qualcomm Shikra interconnect providers support adjusting the
> + bandwidth requirements between the various NoC fabrics.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,shikra-config-noc
> + - qcom,shikra-mem-noc-core
> + - qcom,shikra-sys-noc
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + minItems: 1
> + maxItems: 4
> +
> + clock-names:
> + minItems: 1
> + maxItems: 4
> +
> +# Child node's properties
> +patternProperties:
> + '^interconnect-[a-z0-9]+$':
> + type: object
> + description:
> + The interconnect providers do not have a separate QoS register space,
> + but share parent's space.
> +
> + $ref: qcom,rpm-common.yaml#
> +
> + properties:
> + compatible:
> + enum:
> + - qcom,shikra-clk-virt
> + - qcom,shikra-mc-virt
> + - qcom,shikra-mmrt-virt
> + - qcom,shikra-mmnrt-virt
> +
> + required:
> + - compatible
> +
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - reg
> +
> +allOf:
> + - $ref: qcom,rpm-common.yaml#
> + - if:
> + properties:
> + compatible:
> + const: qcom,shikra-mem-noc-core
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: GPU-NoC AXI clock
> +
> + clock-names:
> + items:
> + - const: gpu_axi
> +
> + - if:
> + properties:
> + compatible:
> + const: qcom,shikra-sys-noc
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: EMAC0-NoC AXI clock.
> + - description: EMAC1-NoC AXI clock.
> + - description: USB2-NoC AXI clock.
> + - description: USB3-NoC AXI clock.
> +
> + clock-names:
> + items:
> + - const: emac0_axi
> + - const: emac1_axi
> + - const: usb2_axi
> + - const: usb3_axi
> +
> + - if:
> + properties:
> + compatible:
> + enum:
> + - qcom,shikra-clk-virt
> + - qcom,shikra-config-noc
> + - qcom,shikra-mc-virt
> + - qcom,shikra-mmrt-virt
> + - qcom,shikra-mmnrt-virt
This if is pointless here, changes nothing and not really correct. Drop
it, I will fix existing bindings.
OTOH, do all NoCs have children? If not, the patternProperties should be
disallowed for such cases. Also clocks should be restricted, see my
patch:
20260503161653.60785-4-krzysztof.kozlowski@oss.qualcomm.com
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-03 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 14:03 [PATCH 0/2] Add interconnect support for Qualcomm Shikra SoC Raviteja Laggyshetty
2026-04-29 14:03 ` [PATCH 1/2] dt-bindings: interconnect: document the RPM Network-On-Chip interconnect in " Raviteja Laggyshetty
2026-05-03 16:17 ` Krzysztof Kozlowski [this message]
2026-05-04 7:17 ` Raviteja Laggyshetty
2026-04-29 14:03 ` [PATCH 2/2] interconnect: qcom: add Shikra interconnect provider driver Raviteja Laggyshetty
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=20260503-enormous-benign-salamander-8d074c@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@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=odelu.kukatla@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--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