From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Alex Elder <elder@linaro.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <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: Re: [PATCH net-next 2/6] net: ipa: kill gsi->virt_raw
Date: Thu, 16 Feb 2023 18:51:08 +0100 [thread overview]
Message-ID: <b0b2ae77-3311-34c8-d1a2-c6f30eca3f1e@intel.com> (raw)
In-Reply-To: <20230215195352.755744-3-elder@linaro.org>
From: Alex Elder <elder@linaro.org>
Date: Wed, 15 Feb 2023 13:53:48 -0600
> Starting at IPA v4.5, almost all GSI registers had their offsets
> changed by a fixed amount (shifted downward by 0xd000). Rather than
> defining offsets for all those registers dependent on version, an
> adjustment was applied for most register accesses. This was
> implemented in commit cdeee49f3ef7f ("net: ipa: adjust GSI register
> addresses"). It was later modified to be a bit more obvious about
> the adjusment, in commit 571b1e7e58ad3 ("net: ipa: use a separate
> pointer for adjusted GSI memory").
[...]
> @@ -142,27 +127,17 @@ int gsi_reg_init(struct gsi *gsi, struct platform_device *pdev)
> return -EINVAL;
> }
>
> - /* Make sure we can make our pointer adjustment if necessary */
> - adjust = gsi->version < IPA_VERSION_4_5 ? 0 : GSI_EE_REG_ADJUST;
> - if (res->start < adjust) {
> - dev_err(dev, "DT memory resource \"gsi\" too low (< %u)\n",
> - adjust);
> - return -EINVAL;
> - }
> -
> gsi->regs = gsi_regs(gsi);
> if (!gsi->regs) {
> dev_err(dev, "unsupported IPA version %u (?)\n", gsi->version);
> return -EINVAL;
> }
>
> - gsi->virt_raw = ioremap(res->start, size);
> - if (!gsi->virt_raw) {
> + gsi->virt = ioremap(res->start, size);
Now that at least one check above went away and the second one might be
or be not correct (I thought ioremap core takes care of this), can't
just devm_platform_ioremap_resource_byname() be used here for simplicity?
> + if (!gsi->virt) {
> dev_err(dev, "unable to remap \"gsi\" memory\n");
> return -ENOMEM;
> }
> - /* Most registers are accessed using an adjusted register range */
> - gsi->virt = gsi->virt_raw - adjust;
>
> return 0;
> }
> @@ -170,7 +145,7 @@ int gsi_reg_init(struct gsi *gsi, struct platform_device *pdev)
> /* Inverse of gsi_reg_init() */
> void gsi_reg_exit(struct gsi *gsi)
> {
> + iounmap(gsi->virt);
(don't forget to remove this unmap if you decide to switch to devm_)
> gsi->virt = NULL;
> - iounmap(gsi->virt_raw);
> - gsi->virt_raw = NULL;
> + gsi->regs = NULL;
> }
[...]
> diff --git a/drivers/net/ipa/reg/gsi_reg-v3.1.c b/drivers/net/ipa/reg/gsi_reg-v3.1.c
> index 651c8a7ed6116..8451d3f8e421e 100644
> --- a/drivers/net/ipa/reg/gsi_reg-v3.1.c
> +++ b/drivers/net/ipa/reg/gsi_reg-v3.1.c
> @@ -8,16 +8,12 @@
> #include "../reg.h"
> #include "../gsi_reg.h"
>
> -/* The inter-EE IRQ registers are relative to gsi->virt_raw (IPA v3.5+) */
> -
> REG(INTER_EE_SRC_CH_IRQ_MSK, inter_ee_src_ch_irq_msk,
> 0x0000c020 + 0x1000 * GSI_EE_AP);
>
> REG(INTER_EE_SRC_EV_CH_IRQ_MSK, inter_ee_src_ev_ch_irq_msk,
> 0x0000c024 + 0x1000 * GSI_EE_AP);
>
> -/* All other register offsets are relative to gsi->virt */
> -
> static const u32 reg_ch_c_cntxt_0_fmask[] = {
> [CHTYPE_PROTOCOL] = GENMASK(2, 0),
> [CHTYPE_DIR] = BIT(3),
> @@ -66,10 +62,6 @@ static const u32 reg_error_log_fmask[] = {
> [ERR_EE] = GENMASK(31, 28),
> };
>
> -REG_FIELDS(ERROR_LOG, error_log, 0x0001f200 + 0x4000 * GSI_EE_AP);
> -
> -REG(ERROR_LOG_CLR, error_log_clr, 0x0001f210 + 0x4000 * GSI_EE_AP);
> -
> REG_STRIDE(CH_C_SCRATCH_0, ch_c_scratch_0,
> 0x0001c060 + 0x4000 * GSI_EE_AP, 0x80);
>
> @@ -152,6 +144,7 @@ REG_FIELDS(GSI_STATUS, gsi_status, 0x0001f000 + 0x4000 * GSI_EE_AP);
>
> static const u32 reg_ch_cmd_fmask[] = {
> [CH_CHID] = GENMASK(7, 0),
> + /* Bits 8-23 reserved */
> [CH_OPCODE] = GENMASK(31, 24),
> };
>
> @@ -159,6 +152,7 @@ REG_FIELDS(CH_CMD, ch_cmd, 0x0001f008 + 0x4000 * GSI_EE_AP);
>
> static const u32 reg_ev_ch_cmd_fmask[] = {
> [EV_CHID] = GENMASK(7, 0),
> + /* Bits 8-23 reserved */
> [EV_OPCODE] = GENMASK(31, 24),
> };
>
[...]
(offtopic)
I hope all those gsi_reg-v*.c are autogenerated? They look pretty scary
to be written and edited manually each time :D
Thanks,
Olek
next prev parent reply other threads:[~2023-02-16 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 19:53 [PATCH net-next 0/6] net: final GSI register updates Alex Elder
2023-02-15 19:53 ` [PATCH net-next 1/6] net: ipa: fix an incorrect assignment Alex Elder
2023-02-15 19:53 ` [PATCH net-next 2/6] net: ipa: kill gsi->virt_raw Alex Elder
2023-02-16 17:51 ` Alexander Lobakin [this message]
2023-02-16 18:11 ` Alex Elder
2023-02-17 11:57 ` Alexander Lobakin
2023-02-17 13:04 ` Alex Elder
2023-03-05 16:58 ` Alex Elder
2023-03-06 10:30 ` Alexander Lobakin
2023-02-15 19:53 ` [PATCH net-next 3/6] net: ipa: kill ev_ch_e_cntxt_1_length_encode() Alex Elder
2023-02-15 19:53 ` [PATCH net-next 4/6] net: ipa: avoid setting an undefined field Alex Elder
2023-02-15 19:53 ` [PATCH net-next 5/6] net: ipa: support different event ring encoding Alex Elder
2023-02-15 19:53 ` [PATCH net-next 6/6] net: ipa: add HW_PARAM_4 GSI register Alex Elder
2023-02-20 7:30 ` [PATCH net-next 0/6] net: final GSI register updates 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=b0b2ae77-3311-34c8-d1a2-c6f30eca3f1e@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.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