From: Rob Herring <robh@kernel.org>
To: Melody Olvera <quic_molvera@quicinc.com>
Cc: Georgi Djakov <djakov@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: interconnect: Add QDU1000/QRU1000 devices
Date: Tue, 20 Dec 2022 12:48:40 -0600 [thread overview]
Message-ID: <167156211955.896464.4722147232675381976.robh@kernel.org> (raw)
In-Reply-To: <20221216230914.21771-2-quic_molvera@quicinc.com>
On Fri, 16 Dec 2022 15:09:13 -0800, Melody Olvera wrote:
> Add separate schema for QDU1000 and QRU1000 interconnect devices
> to document the different NoCs on these platforms.
>
> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> ---
> .../interconnect/qcom,qdu1000-rpmh.yaml | 70 +++++++++++++
> .../interconnect/qcom,qdu1000-rpmh.h | 98 +++++++++++++++++++
> 2 files changed, 168 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,qdu1000-rpmh.yaml
> create mode 100644 include/dt-bindings/interconnect/qcom,qdu1000-rpmh.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-12-20 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 23:09 [PATCH v5 0/2] Add interconnect support for QDU1000/QRU1000 SoCs Melody Olvera
2022-12-16 23:09 ` [PATCH v5 1/2] dt-bindings: interconnect: Add QDU1000/QRU1000 devices Melody Olvera
2022-12-20 18:48 ` Rob Herring [this message]
2022-12-21 7:58 ` Krzysztof Kozlowski
2022-12-16 23:09 ` [PATCH v5 2/2] interconnect: qcom: Add QDU1000/QRU1000 interconnect driver Melody Olvera
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=167156211955.896464.4722147232675381976.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_molvera@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=robh+dt@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®