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>, <evgreen@chromium.org>,
<dianders@chromium.org>, <swboyd@chromium.org>,
<mka@chromium.org>, <krzysztof.kozlowski@canonical.com>,
Sibi Sankar <quic_sibis@quicinc.com>
Subject: [PATCH 0/3] Add support for proxy interconnect bandwidth votes
Date: Mon, 14 Feb 2022 10:04:09 +0530 [thread overview]
Message-ID: <1644813252-12897-1-git-send-email-quic_sibis@quicinc.com> (raw)
Add support for proxy interconnect bandwidth votes during modem bootup on
SC7280 SoCs.
Sibi Sankar (3):
dt-bindings: remoteproc: qcom: Add interconnects property
remoteproc: qcom_q6v5_mss: Add support for interconnect bandwidth
voting
arm64: dts: qcom: sc7280: Add proxy interconnect requirements for
modem
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 23 ++++++
arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi | 2 +
drivers/remoteproc/qcom_q6v5_mss.c | 95 +++++++++++++++++++++-
3 files changed, 119 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2022-02-14 4:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 4:34 Sibi Sankar [this message]
2022-02-14 4:34 ` [PATCH 1/3] dt-bindings: remoteproc: qcom: Add interconnects property Sibi Sankar
2022-02-14 7:28 ` Krzysztof Kozlowski
2022-02-14 4:34 ` [PATCH 2/3] remoteproc: qcom_q6v5_mss: Add support for interconnect bandwidth voting Sibi Sankar
2022-02-22 18:33 ` Bjorn Andersson
2022-02-14 4:34 ` [PATCH 3/3] arm64: dts: qcom: sc7280: Add proxy interconnect requirements for modem Sibi Sankar
2022-02-24 19:59 ` Bjorn Andersson
2022-04-04 23:17 ` [PATCH 0/3] Add support for proxy interconnect bandwidth votes Stephen Boyd
2022-05-10 10:59 ` Sibi Sankar
2022-05-10 11:03 ` 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=1644813252-12897-1-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=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=krzysztof.kozlowski@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).