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/8] net: ipa: determine GSI register offsets differently
Date: Fri, 10 Feb 2023 13:36:47 -0600 [thread overview]
Message-ID: <20230210193655.460225-1-elder@linaro.org> (raw)
This series changes the way GSI register offset are specified, using
the "reg" mechanism currently used for IPA registers. A follow-on
series will extend this work so fields within GSI registers are also
specified this way.
The first patch rearranges the GSI register initialization code so
it is similar to the way it's done for the IPA registers. The
second identifies all the GSI registers in an enumerated type.
The third introduces "gsi_reg-v3.1.c" and uses the "reg" code to
define one GSI register offset. The second-to-last patch just
adds "gsi_reg-v3.5.1.c", because that version introduces a new
register not previously defined. All the rest just define the
rest of the GSI register offsets using the "reg" mechanism.
Note that, to have continued lines align with an open parenthesis,
new files created in this series cause some checkpatch warnings.
-Alex
Alex Elder (8):
net: ipa: introduce gsi_reg_init()
net: ipa: introduce GSI register IDs
net: ipa: start creating GSI register definitions
net: ipa: add more GSI register definitions
net: ipa: define IPA v3.1 GSI event ring register offsets
net: ipa: define IPA v3.1 GSI interrupt register offsets
net: ipa: add "gsi_v3.5.1.c"
net: ipa: define IPA remaining GSI register offsets
drivers/net/ipa/Makefile | 9 +-
drivers/net/ipa/gsi.c | 340 ++++++++++++++++++---------
drivers/net/ipa/gsi.h | 4 +-
drivers/net/ipa/gsi_reg.c | 168 +++++++++++++
drivers/net/ipa/gsi_reg.h | 258 ++++++++------------
drivers/net/ipa/reg/gsi_reg-v3.1.c | 201 ++++++++++++++++
drivers/net/ipa/reg/gsi_reg-v3.5.1.c | 204 ++++++++++++++++
7 files changed, 903 insertions(+), 281 deletions(-)
create mode 100644 drivers/net/ipa/gsi_reg.c
create mode 100644 drivers/net/ipa/reg/gsi_reg-v3.1.c
create mode 100644 drivers/net/ipa/reg/gsi_reg-v3.5.1.c
--
2.34.1
next reply other threads:[~2023-02-10 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 19:36 Alex Elder [this message]
2023-02-10 19:36 ` [PATCH net-next 1/8] net: ipa: introduce gsi_reg_init() Alex Elder
2023-02-10 19:36 ` [PATCH net-next 2/8] net: ipa: introduce GSI register IDs Alex Elder
2023-02-10 19:36 ` [PATCH net-next 3/8] net: ipa: start creating GSI register definitions Alex Elder
2023-02-10 19:36 ` [PATCH net-next 4/8] net: ipa: add more " Alex Elder
2023-02-10 19:36 ` [PATCH net-next 5/8] net: ipa: define IPA v3.1 GSI event ring register offsets Alex Elder
2023-02-10 19:36 ` [PATCH net-next 6/8] net: ipa: define IPA v3.1 GSI interrupt " Alex Elder
2023-02-10 19:36 ` [PATCH net-next 7/8] net: ipa: add "gsi_v3.5.1.c" Alex Elder
2023-02-10 19:36 ` [PATCH net-next 8/8] net: ipa: define IPA remaining GSI register offsets Alex Elder
2023-02-13 10:00 ` [PATCH net-next 0/8] net: ipa: determine GSI register offsets differently 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=20230210193655.460225-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