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 v2 0/7] net: ipa: use bulk interconnect interfaces
Date: Wed, 9 Mar 2022 13:20:30 -0600 [thread overview]
Message-ID: <20220309192037.667879-1-elder@linaro.org> (raw)
The IPA code currently enables and disables interconnects by setting
the bandwidth of each to a non-zero value, or to zero. The
interconnect API now supports enable/disable functions, so we can
use those instead. In addition, the interconnect API provides bulk
interfaces that allow all interconnects to be operated on at once.
This series converts the IPA driver to use the bulk enable and
disable interfaces. In the process it uses some existing data
structures rather than defining new ones.
Version 2 contains the same code as version 1; it's just rebased.
Now that commit 1dba41c9d2e2d ("net: ipa: add an interconnect
dependency") is in net-next/master the COMPILE_TEST build error
reported for the original version should be gone.
https://lore.kernel.org/all/20220204202336.67c95e15@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com/
-Alex
Alex Elder (7):
net: ipa: kill struct ipa_interconnect
net: ipa: use icc_enable() and icc_disable()
net: ipa: use interconnect bulk enable/disable operations
net: ipa: use bulk operations to set up interconnects
net: ipa: use bulk interconnect initialization
net: ipa: embed interconnect array in the power structure
net: ipa: use IPA power device pointer
drivers/net/ipa/ipa_power.c | 178 +++++++++---------------------------
1 file changed, 42 insertions(+), 136 deletions(-)
--
2.32.0
next reply other threads:[~2022-03-09 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:20 Alex Elder [this message]
2022-03-09 19:20 ` [PATCH net-next v2 1/7] net: ipa: kill struct ipa_interconnect Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 2/7] net: ipa: use icc_enable() and icc_disable() Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 3/7] net: ipa: use interconnect bulk enable/disable operations Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 4/7] net: ipa: use bulk operations to set up interconnects Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 5/7] net: ipa: use bulk interconnect initialization Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 6/7] net: ipa: embed interconnect array in the power structure Alex Elder
2022-03-11 5:25 ` Jakub Kicinski
2022-03-11 13:02 ` Alex Elder
2022-03-09 19:20 ` [PATCH net-next v2 7/7] net: ipa: use IPA power device pointer Alex Elder
2022-03-11 5:30 ` [PATCH net-next v2 0/7] net: ipa: use bulk interconnect interfaces patchwork-bot+netdevbpf
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=20220309192037.667879-1-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).