From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@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>,
Del Regno <angelogioacchino.delregno@somainline.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
Andy Gross <agross@codeaurora.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] dt-bindings: interconnect: add Qualcomm MSM8998 NoC
Date: Tue, 20 Oct 2026 10:24:24 +0200 [thread overview]
Message-ID: <20261020-daft-competent-saluki-a080c7@quoll> (raw)
In-Reply-To: <20261019-msm8998-icc-v1-1-c2da3934b6c8@oss.qualcomm.com>
On Mon, Oct 19, 2026 at 05:12:39PM +0300, Dmitry Baryshkov wrote:
> +properties:
> + compatible:
> + enum:
> + - qcom,msm8998-a1noc
> + - qcom,msm8998-a2noc
> + - qcom,msm8998-bimc
> + - qcom,msm8998-cnoc
> + - qcom,msm8998-gnoc
> + - qcom,msm8998-mnoc
> + - qcom,msm8998-mnoc-ahb
> + - qcom,msm8998-snoc
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + minItems: 1
> + maxItems: 4
> +
> + clock-names:
> + minItems: 1
> + maxItems: 4
...
> + - if:
> + properties:
> + compatible:
> + const: qcom,msm8998-mnoc-ahb
> +
> + then:
> + description:
> + The MMSS AHB NoC shares its register space with the MMSS NoC, so it is
> + described as a child of the latter and has no register range of its own.
> +
> + properties:
reg: false
> + clocks:
> + items:
> + - description: MMSS AHB Clock
> +
> + clock-names:
> + const: bus
> +
> + required:
> + - clocks
> + - clock-names
> +
> + else:
> + required:
> + - reg
> +
> + - if:
> + properties:
> + compatible:
> + enum:
> + - qcom,msm8998-bimc
> + - qcom,msm8998-gnoc
> +
> + then:
> + properties:
> + clocks: false
> + clock-names: false
> +
unevaluatedProperties should go here, just before the example
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,gcc-msm8998.h>
> + #include <dt-bindings/clock/qcom,mmcc-msm8998.h>
> +
> + interconnect@1008300 {
> + compatible = "qcom,msm8998-bimc";
> + reg = <0x01008300 0x77d00>;
> + #interconnect-cells = <2>;
> + };
> +
> + interconnect@1740000 {
> + compatible = "qcom,msm8998-mnoc";
> + reg = <0x01740000 0x10000>;
> + clocks = <&mmcc MNOC_AHB_CLK>, <&mmcc MNOC_MAXI_CLK>;
> + clock-names = "iface", "mnoc_bus";
> + #interconnect-cells = <2>;
> +
> + interconnect-mnoc-ahb {
I do not see how this can validate. You do not allow any children in
your binding. Your tpo-level properties should define all possible
properties and nodes.
also, name should be just "interconnect"
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-20 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:12 [PATCH 0/8] interconnect: qcom: implement support for MSM8998 Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 1/8] dt-bindings: interconnect: add Qualcomm MSM8998 NoC Dmitry Baryshkov
2026-10-20 8:24 ` Krzysztof Kozlowski [this message]
2026-10-19 14:12 ` [PATCH 2/8] soc: qcom: smd-rpm: Handle zero-length errors Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 3/8] interconnect: qcom: icc-rpm: depopulate SMD RPM child NoCs Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 4/8] interconnect: qcom: icc-rpm: skip duplicate SMD RPM node votes Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 5/8] interconnect: qcom: icc-rpm: Allow negative QoS offset Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 6/8] interconnect: qcom: add MSM8998 interconnect provider Dmitry Baryshkov
2026-10-19 14:12 ` [PATCH 7/8] arm64: dts: qcom: msm8998: add interconnect provider nodes Dmitry Baryshkov
2026-10-20 7:11 ` Konrad Dybcio
2026-10-19 14:12 ` [PATCH 8/8] arm64: dts: qcom: msm8998: wire up interconnect paths Dmitry Baryshkov
2026-10-20 7:16 ` 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=20261020-daft-competent-saluki-a080c7@quoll \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=agross@codeaurora.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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=robh@kernel.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
all inboxes | Powered by JetHome®