From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: caleb.connolly@linaro.org, mka@chromium.org,
evgreen@chromium.org, andersson@kernel.org,
quic_cpratapa@quicinc.com, quic_avuyyuru@quicinc.com,
quic_jponduru@quicinc.com, quic_subashab@quicinc.com,
elder@kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/9] net: ipa: prepare for GSI register updtaes
Date: Wed, 8 Feb 2023 14:56:44 -0600 [thread overview]
Message-ID: <20230208205653.177700-1-elder@linaro.org> (raw)
An upcoming series (or two) will convert the definitions of GSI
registers used by IPA so they use the "IPA reg" mechanism to specify
register offsets and their fields. This will simplify implementing
the fairly large number of changes required in GSI registers to
support more than 32 GSI channels (introduced in IPA v5.0).
A few minor problems and inconsistencies were found, and they're
fixed here. The last three patches in this series change the
"ipa_reg" code to separate the IPA-specific part (the base virtual
address, basically) from the generic register part, and the now-
generic code is renamed to use just "reg_" or "REG_" as a prefix
rather than "ipa_reg" or "IPA_REG_".
-Alex
Alex Elder (9):
net: ipa: generic command param fix
net: ipa: get rid of ipa->reg_addr
net: ipa: add some new IPA versions
net: ipa: tighten up IPA register validity checking
net: ipa: use bitmasks for GSI IRQ values
net: ipa: GSI register cleanup
net: ipa: start generalizing "ipa_reg"
net: ipa: generalize register offset functions
net: ipa: generalize register field functions
drivers/net/ipa/gsi.c | 82 +++++---
drivers/net/ipa/gsi_reg.h | 109 +++++------
drivers/net/ipa/ipa.h | 4 +-
drivers/net/ipa/ipa_cmd.c | 6 +-
drivers/net/ipa/ipa_endpoint.c | 205 ++++++++++---------
drivers/net/ipa/ipa_interrupt.c | 29 ++-
drivers/net/ipa/ipa_main.c | 114 +++++------
drivers/net/ipa/ipa_mem.c | 14 +-
drivers/net/ipa/ipa_reg.c | 90 +++++----
drivers/net/ipa/ipa_reg.h | 139 ++-----------
drivers/net/ipa/ipa_resource.c | 16 +-
drivers/net/ipa/ipa_table.c | 35 ++--
drivers/net/ipa/ipa_uc.c | 6 +-
drivers/net/ipa/ipa_version.h | 6 +-
drivers/net/ipa/reg.h | 133 +++++++++++++
drivers/net/ipa/reg/ipa_reg-v3.1.c | 277 +++++++++++++-------------
drivers/net/ipa/reg/ipa_reg-v3.5.1.c | 263 +++++++++++++------------
drivers/net/ipa/reg/ipa_reg-v4.11.c | 265 +++++++++++++------------
drivers/net/ipa/reg/ipa_reg-v4.2.c | 249 ++++++++++++------------
drivers/net/ipa/reg/ipa_reg-v4.5.c | 281 +++++++++++++--------------
drivers/net/ipa/reg/ipa_reg-v4.7.c | 265 +++++++++++++------------
drivers/net/ipa/reg/ipa_reg-v4.9.c | 265 +++++++++++++------------
22 files changed, 1451 insertions(+), 1402 deletions(-)
create mode 100644 drivers/net/ipa/reg.h
--
2.34.1
next reply other threads:[~2023-02-08 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 20:56 Alex Elder [this message]
2023-02-08 20:56 ` [PATCH net-next 1/9] net: ipa: generic command param fix Alex Elder
2023-02-08 20:56 ` [PATCH net-next 2/9] net: ipa: get rid of ipa->reg_addr Alex Elder
2023-02-08 20:56 ` [PATCH net-next 3/9] net: ipa: add some new IPA versions Alex Elder
2023-02-08 20:56 ` [PATCH net-next 4/9] net: ipa: tighten up IPA register validity checking Alex Elder
2023-02-08 20:56 ` [PATCH net-next 5/9] net: ipa: use bitmasks for GSI IRQ values Alex Elder
2023-02-08 20:56 ` [PATCH net-next 6/9] net: ipa: GSI register cleanup Alex Elder
2023-02-08 20:56 ` [PATCH net-next 7/9] net: ipa: start generalizing "ipa_reg" Alex Elder
2023-02-08 20:56 ` [PATCH net-next 8/9] net: ipa: generalize register offset functions Alex Elder
2023-02-08 20:56 ` [PATCH net-next 9/9] net: ipa: generalize register field functions Alex Elder
2023-02-10 8:50 ` [PATCH net-next 0/9] net: ipa: prepare for GSI register updtaes 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=20230208205653.177700-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=evgreen@chromium.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=pabeni@redhat.com \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.com \
/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).