From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, kuba@kernel.org
Cc: djakov@kernel.org, bjorn.andersson@linaro.org, mka@chromium.org,
evgreen@chromium.org, cpratapa@codeaurora.org,
avuyyuru@codeaurora.org, jponduru@codeaurora.org,
subashab@codeaurora.org, elder@kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 2/7] net: ipa: use icc_enable() and icc_disable()
Date: Fri, 4 Feb 2022 13:50:39 -0600 [thread overview]
Message-ID: <20220204195044.1082026-3-elder@linaro.org> (raw)
In-Reply-To: <20220204195044.1082026-1-elder@linaro.org>
The interconnect framework now provides the ability to enable and
disable interconnects without having to change their recorded
"enabled" bandwidth value. Use this mechanism, rather than setting
the bandwidth values to zero and non-zero respectively to disable
and enable the IPA interconnects.
Disable each interconnect before setting its "enabled" average and
peak bandwidth values. Thereafter, enable and disable interconnects
when required rather than setting their bandwidths.
Signed-off-by: Alex Elder <elder@linaro.org>
---
drivers/net/ipa/ipa_power.c | 24 +++++++++++++++++-------
1 file changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/net/ipa/ipa_power.c b/drivers/net/ipa/ipa_power.c
index 28be0e45cccfd..ec2ebc74edb8b 100644
--- a/drivers/net/ipa/ipa_power.c
+++ b/drivers/net/ipa/ipa_power.c
@@ -75,17 +75,29 @@ static int ipa_interconnect_init_one(struct device *dev,
const struct ipa_interconnect_data *data)
{
struct icc_path *path;
+ int ret;
path = of_icc_get(dev, data->name);
if (IS_ERR(path)) {
- int ret = PTR_ERR(path);
-
+ ret = PTR_ERR(path);
dev_err_probe(dev, ret, "error getting %s interconnect\n",
data->name);
return ret;
}
+ /* All interconnects are initially disabled */
+ (void)icc_disable(path);
+
+ /* Set the bandwidth values to be used when enabled */
+ ret = icc_set_bw(path, data->average_bandwidth, data->peak_bandwidth);
+ if (ret) {
+ dev_err(dev, "error %d setting %s interconnect bandwidths\n",
+ ret, data->name);
+
+ return ret;
+ }
+
interconnect->path = path;
interconnect->name = data->name;
interconnect->avg_bw = data->average_bandwidth;
@@ -154,9 +166,7 @@ static int ipa_interconnect_enable(struct ipa *ipa)
interconnect = power->interconnect;
for (i = 0; i < power->interconnect_count; i++) {
- ret = icc_set_bw(interconnect->path,
- interconnect->avg_bw,
- interconnect->peak_bw);
+ ret = icc_enable(interconnect->path);
if (ret) {
dev_err(&ipa->pdev->dev,
"error %d enabling %s interconnect\n",
@@ -170,7 +180,7 @@ static int ipa_interconnect_enable(struct ipa *ipa)
out_unwind:
while (interconnect-- > power->interconnect)
- (void)icc_set_bw(interconnect->path, 0, 0);
+ (void)icc_disable(interconnect->path);
return ret;
}
@@ -189,7 +199,7 @@ static int ipa_interconnect_disable(struct ipa *ipa)
interconnect = power->interconnect + count;
while (count--) {
interconnect--;
- ret = icc_set_bw(interconnect->path, 0, 0);
+ ret = icc_disable(interconnect->path);
if (ret) {
dev_err(dev, "error %d disabling %s interconnect\n",
ret, interconnect->name);
--
2.32.0
next prev parent reply other threads:[~2022-02-04 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 19:50 [PATCH net-next 0/7] net: ipa: use bulk interconnect interfaces Alex Elder
2022-02-04 19:50 ` [PATCH net-next 1/7] net: ipa: kill struct ipa_interconnect Alex Elder
2022-02-04 19:50 ` Alex Elder [this message]
2022-02-04 19:50 ` [PATCH net-next 3/7] net: ipa: use interconnect bulk enable/disable operations Alex Elder
2022-02-05 4:23 ` Jakub Kicinski
2022-02-05 14:35 ` Alex Elder
2022-02-04 19:50 ` [PATCH net-next 4/7] net: ipa: use bulk operations to set up interconnects Alex Elder
2022-02-04 19:50 ` [PATCH net-next 5/7] net: ipa: use bulk interconnect initialization Alex Elder
2022-02-04 19:50 ` [PATCH net-next 6/7] net: ipa: embed interconnect array in the power structure Alex Elder
2022-02-04 19:50 ` [PATCH net-next 7/7] net: ipa: use IPA power device pointer Alex Elder
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=20220204195044.1082026-3-elder@linaro.org \
--to=elder@linaro.org \
--cc=avuyyuru@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=djakov@kernel.org \
--cc=elder@kernel.org \
--cc=evgreen@chromium.org \
--cc=jponduru@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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).