From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Adam Skladowski <a39.skl@gmail.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Danila Tikhonov <danila@jiaxyga.com>,
Vladimir Lypak <vladimir.lypak@gmail.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
Mike Tipton <quic_mdtipton@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in QCS615 SoC
Date: Tue, 24 Sep 2024 21:03:39 +0200 [thread overview]
Message-ID: <902310fb-14fd-42ff-bcac-7814cbc0d635@kernel.org> (raw)
In-Reply-To: <20240924143958.25-2-quic_rlaggysh@quicinc.com>
On 24/09/2024 16:39, Raviteja Laggyshetty wrote:
> Document the RPMh Network-On-Chip Interconnect of the QCS615 platform.
>
> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
...
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + gem_noc: interconnect@9680000 {
> + compatible = "qcom,qcs615-gem-noc";
> + reg = <0x9680000 0x3E200>;
If there is going to be new version, then lowercase hex.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-24 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 14:39 [PATCH 0/2] Add interconnect support for QCS615 SoC Raviteja Laggyshetty
2024-09-24 14:39 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2024-09-24 19:03 ` Krzysztof Kozlowski [this message]
2024-09-24 14:39 ` [PATCH 2/2] interconnect: qcom: add QCS615 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=902310fb-14fd-42ff-bcac-7814cbc0d635@kernel.org \
--to=krzk@kernel.org \
--cc=a39.skl@gmail.com \
--cc=conor+dt@kernel.org \
--cc=danila@jiaxyga.com \
--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=neil.armstrong@linaro.org \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_rlaggysh@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=vladimir.lypak@gmail.com \
/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