From: Niklas Cassel <cassel@kernel.org>
To: Aksh Garg <a-garg7@ti.com>, Koichiro Den <den@valinux.co.jp>
Cc: linux-pci@vger.kernel.org, jingoohan1@gmail.com, mani@kernel.org,
lpieralisi@kernel.org, kwilczynski@kernel.org, robh@kernel.org,
bhelgaas@google.com, Zhiqiang.Hou@nxp.com,
gustavo.pimentel@synopsys.com, linux-kernel@vger.kernel.org,
s-vadapalli@ti.com, danishanwar@ti.com
Subject: Re: [PATCH v4 2/3] PCI: dwc: ep: Add per-PF BAR and inbound ATU mapping support
Date: Thu, 29 Jan 2026 15:14:51 +0100 [thread overview]
Message-ID: <aXtrW7viGZfMNZur@ryzen> (raw)
In-Reply-To: <20260129091753.490167-3-a-garg7@ti.com>
On Thu, Jan 29, 2026 at 02:47:52PM +0530, Aksh Garg wrote:
> -static void dw_pcie_ep_clear_ib_maps(struct dw_pcie_ep *ep, enum pci_barno bar)
> +static void dw_pcie_ep_clear_ib_maps(struct dw_pcie_ep *ep, u8 func_no, enum pci_barno bar)
> {
> + struct dw_pcie_ep_func *ep_func = dw_pcie_ep_get_func_from_ep(ep, func_no);
> struct dw_pcie *pci = to_dw_pcie_from_ep(ep);
> struct device *dev = pci->dev;
> unsigned int i, num;
> @@ -152,18 +157,18 @@ static void dw_pcie_ep_clear_ib_maps(struct dw_pcie_ep *ep, enum pci_barno bar)
> u32 *indexes;
Hello Aksh,
Considering that all other functions that you have modified, you have added a:
if (!ep_func)
return;
I think you should do the same to this function.
>
> /* Tear down the BAR Match Mode mapping, if any. */
> - if (ep->bar_to_atu[bar]) {
> - atu_index = ep->bar_to_atu[bar] - 1;
> + if (ep_func->bar_to_atu[bar]) {
> + atu_index = ep_func->bar_to_atu[bar] - 1;
> dw_pcie_disable_atu(pci, PCIE_ATU_REGION_DIR_IB, atu_index);
> clear_bit(atu_index, ep->ib_window_map);
> - ep->bar_to_atu[bar] = 0;
> + ep_func->bar_to_atu[bar] = 0;
Not related to your patch,
Koichiro (he is on To:),
don't you think that it would be clearer if we had a:
return;
here...
I mean, a BAR can either have a BAR match mode mapping or a subrange mapping,
but not both... So continuing executing code beyond this point seems pointless,
possibly even confusing.
> }
>
> /* Tear down all Address Match Mode mappings, if any. */
> - indexes = ep->ib_atu_indexes[bar];
> - num = ep->num_ib_atu_indexes[bar];
> - ep->ib_atu_indexes[bar] = NULL;
> - ep->num_ib_atu_indexes[bar] = 0;
> + indexes = ep_func->ib_atu_indexes[bar];
> + num = ep_func->num_ib_atu_indexes[bar];
> + ep_func->ib_atu_indexes[bar] = NULL;
> + ep_func->num_ib_atu_indexes[bar] = 0;
> if (!indexes)
> return;
Sure, I see that this code will do a return here...
So there will be no harm done, but, having a simple return above
would make it extra clear to the reader that is is always one or
the other... you cannot have both.
If you agree, perhaps you could send a one liner patch?
> for (i = 0; i < num; i++) {
next prev parent reply other threads:[~2026-01-29 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 9:17 [PATCH v4 0/3] PCI: dwc: ep: Enhance multi-function endpoint support Aksh Garg
2026-01-29 9:17 ` [PATCH v4 1/3] PCI: dwc: ep: Fix resizable BAR support for multi-PF configurations Aksh Garg
2026-01-29 9:17 ` [PATCH v4 2/3] PCI: dwc: ep: Add per-PF BAR and inbound ATU mapping support Aksh Garg
2026-01-29 14:14 ` Niklas Cassel [this message]
2026-01-30 2:21 ` Koichiro Den
2026-01-30 9:57 ` Niklas Cassel
2026-01-30 17:16 ` Koichiro Den
2026-01-30 22:51 ` Niklas Cassel
2026-01-31 13:42 ` Koichiro Den
2026-01-30 4:12 ` Aksh Garg
2026-01-30 9:53 ` Niklas Cassel
2026-01-30 10:39 ` Aksh Garg
2026-01-30 10:47 ` Niklas Cassel
2026-01-30 10:52 ` Aksh Garg
2026-01-29 9:17 ` [PATCH v4 3/3] PCI: dwc: ep: Add comment explaining controller-level PTM access Aksh Garg
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=aXtrW7viGZfMNZur@ryzen \
--to=cassel@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=a-garg7@ti.com \
--cc=bhelgaas@google.com \
--cc=danishanwar@ti.com \
--cc=den@valinux.co.jp \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.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