From: Sibi Sankar <quic_sibis@quicinc.com>
To: <bjorn.andersson@linaro.org>, <robh+dt@kernel.org>
Cc: <ohad@wizery.com>, <agross@kernel.org>,
<mathieu.poirier@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <swboyd@chromium.org>,
<mka@chromium.org>, <krzysztof.kozlowski+dt@linaro.org>,
Sibi Sankar <quic_sibis@quicinc.com>
Subject: [PATCH v3 1/2] arm64: dts: qcom: sc7280: Add proxy interconnect requirements for modem
Date: Wed, 11 May 2022 13:49:21 +0530 [thread overview]
Message-ID: <1652257162-23874-2-git-send-email-quic_sibis@quicinc.com> (raw)
In-Reply-To: <1652257162-23874-1-git-send-email-quic_sibis@quicinc.com>
Add interconnects that are required to be proxy voted upon during modem
bootup on SC7280 SoCs.
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
---
arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
index 9f4a9c263c35..91aad86cc708 100644
--- a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi
@@ -88,6 +88,7 @@
status = "okay";
compatible = "qcom,sc7280-mss-pil";
iommus = <&apps_smmu 0x124 0x0>, <&apps_smmu 0x488 0x7>;
+ interconnects = <&mc_virt MASTER_LLCC 0 &mc_virt SLAVE_EBI1 0>;
memory-region = <&mba_mem>, <&mpss_mem>;
};
--
2.7.4
next prev parent reply other threads:[~2022-05-11 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 8:19 [PATCH v3 0/2] Add support for proxy interconnect bandwidth votes Sibi Sankar
2022-05-11 8:19 ` Sibi Sankar [this message]
2022-05-11 21:09 ` [PATCH v3 1/2] arm64: dts: qcom: sc7280: Add proxy interconnect requirements for modem Stephen Boyd
2022-05-11 8:19 ` [PATCH v3 2/2] dt-bindings: remoteproc: qcom: Add SC7280 MSS bindings Sibi Sankar
2022-05-11 16:59 ` Matthias Kaehlcke
2022-05-12 6:45 ` Sibi Sankar
2022-05-11 18:10 ` Krzysztof Kozlowski
2022-05-12 7:11 ` Sibi Sankar
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=1652257162-23874-2-git-send-email-quic_sibis@quicinc.com \
--to=quic_sibis@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mka@chromium.org \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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®