From: Niklas Cassel <cassel@kernel.org>
To: Koichiro Den <den@valinux.co.jp>
Cc: jingoohan1@gmail.com, mani@kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
Frank.Li@nxp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] PCI: endpoint: Add BAR subrange mapping support
Date: Thu, 8 Jan 2026 10:59:30 +0100 [thread overview]
Message-ID: <aV-AApRHXLOTEwm3@ryzen> (raw)
In-Reply-To: <aV9638ebwqc4bsbd@ryzen>
On Thu, Jan 08, 2026 at 10:37:35AM +0100, Niklas Cassel wrote:
> The memcpy in dw_pcie_ep_get_features() is a bit ugly.
> I guess the alternative is to change all the DWC based glue drivers
> to return a "struct pci_epc_features*" instead of a "const struct pci_epc_features*"
> such that dw_pcie_ep_get_features() can simply set subrange_mapping = true in the
> struct pci_epc_features returned by the glue driver.
I think the best way it probably to create another patch,
that will be patch 2 out of 3 in the series, which changes:
https://github.com/torvalds/linux/blob/v6.19-rc4/drivers/pci/controller/dwc/pcie-designware.h#L449
from:
const struct pci_epc_features* (*get_features)(struct dw_pcie_ep *ep);
to:
struct pci_epc_features* (*get_features)(struct dw_pcie_ep *ep);
and which does the equivalent change in all the DWC based glue drivers.
That way, dw_pcie_ep_get_features() can simply set subrange_mapping = true
in the struct pci_epc_features returned by the glue driver.
Note that the function dw_pcie_ep_get_features() itself should still return:
"static const struct pci_epc_features*"
(Since this represents the DWC midlayer driver level.)
It is only the DWC based glue drivers (lower level drivers) that should drop
the const.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-08 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 4:41 [PATCH v4 0/2] PCI: endpoint: BAR subrange mapping support Koichiro Den
2026-01-08 4:41 ` [PATCH v4 1/2] PCI: endpoint: Add " Koichiro Den
2026-01-08 9:37 ` Niklas Cassel
2026-01-08 9:41 ` Niklas Cassel
2026-01-08 9:59 ` Niklas Cassel [this message]
2026-01-08 16:39 ` Koichiro Den
2026-01-08 4:41 ` [PATCH v4 2/2] PCI: dwc: ep: Support BAR subrange inbound mapping via Address Match Mode iATU Koichiro Den
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=aV-AApRHXLOTEwm3@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--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 \
/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