From: Rob Herring <robh@kernel.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-pm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Loic Poulain <loic.poulain@linaro.org>,
Georgi Djakov <djakov@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/6] dt-bindings: interconnect: Add Qualcomm QCM2290 NoC support
Date: Mon, 13 Dec 2021 16:14:59 -0600 [thread overview]
Message-ID: <YbfF4/F4B8dZ1s5M@robh.at.kernel.org> (raw)
In-Reply-To: <20211206075808.18124-6-shawn.guo@linaro.org>
On Mon, 06 Dec 2021 15:58:07 +0800, Shawn Guo wrote:
> Add bindings for Qualcomm QCM2290 Network-On-Chip interconnect devices.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
> .../bindings/interconnect/qcom,qcm2290.yaml | 137 ++++++++++++++++++
> .../dt-bindings/interconnect/qcom,qcm2290.h | 94 ++++++++++++
> 2 files changed, 231 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml
> create mode 100644 include/dt-bindings/interconnect/qcom,qcm2290.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-13 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 7:58 [PATCH v3 0/6] Add QCM2290 interconnect support Shawn Guo
2021-12-06 7:58 ` [PATCH v3 1/6] interconnect: icc-rpm: Use NOC_QOS_MODE_INVALID for qos_mode check Shawn Guo
2021-12-06 7:58 ` [PATCH v3 2/6] interconnect: icc-rpm: Define ICC device type Shawn Guo
2021-12-06 7:58 ` [PATCH v3 3/6] interconnect: icc-rpm: Add QNOC type QoS support Shawn Guo
2021-12-06 7:58 ` [PATCH v3 4/6] interconnect: icc-rpm: Support child NoC device probe Shawn Guo
2021-12-06 7:58 ` [PATCH v3 5/6] dt-bindings: interconnect: Add Qualcomm QCM2290 NoC support Shawn Guo
2021-12-13 22:14 ` Rob Herring [this message]
2021-12-06 7:58 ` [PATCH v3 6/6] interconnect: qcom: Add QCM2290 driver support Shawn Guo
2021-12-13 22:28 ` [PATCH v3 0/6] Add QCM2290 interconnect support Georgi Djakov
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=YbfF4/F4B8dZ1s5M@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).