From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Shawn Guo <shawn.guo@linaro.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stephan Gerhold <stephan@gerhold.net>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: [PATCH 0/4] Rework rpm-icc QoS settings
Date: Tue, 26 Mar 2024 20:42:31 +0100 [thread overview]
Message-ID: <20240326-topic-rpm_icc_qos_cleanup-v1-0-357e736792be@linaro.org> (raw)
Currently, the QoS settings take up a lot of space and are scattered all
over the nodes, even though the config is only applied once and it's not
a direct property of the nodes themselves.
This series aims to make things better in this regard and contains some
fly-by fixes.
More fixes and cleanups uncovered after the making of this coming soon..
Didn't cause any spontaneous explosions on 6115 and 8996.
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
Konrad Dybcio (4):
interconnect: qcom: sm6115: Unspaghettify SNoC QoS port numbering
interconnect: qcom: qcm2290: Fix mas_snoc_bimc QoS port assignment
interconnect: qcom: icc-rpm: Make simple functions return void
interconnect: qcom: icc-rpm: Remodel how QoS settings are stored
drivers/interconnect/qcom/icc-rpm.c | 187 ++++++-------
drivers/interconnect/qcom/icc-rpm.h | 13 +-
drivers/interconnect/qcom/msm8909.c | 268 ++++++++++---------
drivers/interconnect/qcom/msm8916.c | 153 ++++++-----
drivers/interconnect/qcom/msm8939.c | 157 ++++++-----
drivers/interconnect/qcom/msm8996.c | 517 +++++++++++++++++-------------------
drivers/interconnect/qcom/qcm2290.c | 416 +++++++++++++++++------------
drivers/interconnect/qcom/sdm660.c | 393 +++++++++++++--------------
drivers/interconnect/qcom/sm6115.c | 242 ++++++++++++-----
9 files changed, 1251 insertions(+), 1095 deletions(-)
---
base-commit: 084c8e315db34b59d38d06e684b1a0dd07d30287
change-id: 20240326-topic-rpm_icc_qos_cleanup-bd8958232f39
Best regards,
--
Konrad Dybcio <konrad.dybcio@linaro.org>
next reply other threads:[~2024-03-26 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 19:42 Konrad Dybcio [this message]
2024-03-26 19:42 ` [PATCH 1/4] interconnect: qcom: sm6115: Unspaghettify SNoC QoS port numbering Konrad Dybcio
2024-03-26 20:13 ` Dmitry Baryshkov
2024-03-26 20:32 ` Konrad Dybcio
2024-03-26 19:42 ` [PATCH 2/4] interconnect: qcom: qcm2290: Fix mas_snoc_bimc QoS port assignment Konrad Dybcio
2024-03-26 20:16 ` Stephan Gerhold
2024-03-26 21:32 ` Konrad Dybcio
2024-03-26 19:42 ` [PATCH 3/4] interconnect: qcom: icc-rpm: Make simple functions return void Konrad Dybcio
2024-03-26 20:14 ` Dmitry Baryshkov
2024-05-08 1:57 ` Mike Tipton
2024-03-26 19:42 ` [PATCH 4/4] interconnect: qcom: icc-rpm: Remodel how QoS settings are stored Konrad Dybcio
2024-03-26 20:57 ` Stephan Gerhold
2024-03-26 21:12 ` Konrad Dybcio
2024-05-08 1:45 ` Mike Tipton
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=20240326-topic-rpm_icc_qos_cleanup-v1-0-357e736792be@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@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=marijn.suijten@somainline.org \
--cc=shawn.guo@linaro.org \
--cc=stephan@gerhold.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).