From: Frank Li <Frank.li@nxp.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>,
Koichiro Den <den@valinux.co.jp>,
Damien Le Moal <dlemoal@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/9] PCI: endpoint: Describe reserved subregions within BARs
Date: Wed, 25 Feb 2026 15:22:57 -0500 [thread overview]
Message-ID: <aZ9aId4t6UWLMkFs@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260225170324.4033466-13-cassel@kernel.org>
On Wed, Feb 25, 2026 at 06:03:25PM +0100, Niklas Cassel wrote:
> From: Koichiro Den <den@valinux.co.jp>
>
> Some endpoint controllers expose platform-owned, fixed register windows
> within a BAR that EPF drivers must not reprogram (e.g. a BAR marked
> BAR_RESERVED). Even in that case, EPF drivers may need to reference a
> well-defined subset of that BAR, e.g. to reuse an integrated DMA
> controller MMIO window as a doorbell target.
>
> Introduce struct pci_epc_bar_rsvd_region and extend struct
> pci_epc_bar_desc so EPC drivers can advertise such fixed subregions in a
> controller-agnostic way.
>
> No functional change for existing users.
>
> Tested-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
> Signed-off-by: Koichiro Den <den@valinux.co.jp>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> include/linux/pci-epc.h | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/include/linux/pci-epc.h b/include/linux/pci-epc.h
> index c22f8a6cf9a3..f7f48f43d370 100644
> --- a/include/linux/pci-epc.h
> +++ b/include/linux/pci-epc.h
> @@ -203,6 +203,30 @@ enum pci_epc_bar_type {
> BAR_64BIT_UPPER,
> };
>
> +/**
> + * enum pci_epc_bar_rsvd_region_type - type of a fixed subregion behind a BAR
> + * @PCI_EPC_BAR_RSVD_DMA_CTRL_MMIO: Integrated DMA controller MMIO window
> + *
> + * BARs marked BAR_RESERVED are owned by the SoC/EPC hardware and must not be
> + * reprogrammed by EPF drivers. Some of them still expose fixed subregions that
> + * EPFs may want to reference (e.g. embedded doorbell fallback).
> + */
> +enum pci_epc_bar_rsvd_region_type {
> + PCI_EPC_BAR_RSVD_DMA_CTRL_MMIO = 0,
> +};
> +
> +/**
> + * struct pci_epc_bar_rsvd_region - fixed subregion behind a BAR
> + * @type: reserved region type
> + * @offset: offset within the BAR aperture
> + * @size: size of the reserved region
> + */
> +struct pci_epc_bar_rsvd_region {
> + enum pci_epc_bar_rsvd_region_type type;
> + resource_size_t offset;
> + resource_size_t size;
> +};
> +
> /**
> * struct pci_epc_bar_desc - hardware description for a BAR
> * @type: the type of the BAR
> @@ -216,11 +240,15 @@ enum pci_epc_bar_type {
> * (If BARx is a 64-bit BAR that an EPF driver is not allowed to
> * touch, then both BARx and BARx+1 must be set to type
> * BAR_RESERVED.)
> + * @nr_rsvd_regions: number of fixed subregions described for BAR_RESERVED
> + * @rsvd_regions: fixed subregions behind BAR_RESERVED
> */
> struct pci_epc_bar_desc {
> enum pci_epc_bar_type type;
> u64 fixed_size;
> bool only_64bit;
> + u8 nr_rsvd_regions;
> + const struct pci_epc_bar_rsvd_region *rsvd_regions;
> };
>
> /**
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-02-25 20:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 17:03 [PATCH v2 0/9] PCI: endpoint: Differentiate between disabled and reserved BARs Niklas Cassel
2026-02-25 17:03 ` [PATCH v2 1/9] PCI: endpoint: Introduce pci_epc_bar_type BAR_64BIT_UPPER Niklas Cassel
2026-02-25 17:03 ` [PATCH v2 2/9] PCI: endpoint: Describe reserved subregions within BARs Niklas Cassel
2026-02-25 20:22 ` Frank Li [this message]
2026-02-25 17:03 ` [PATCH v2 3/9] PCI: dw-rockchip: Describe RK3588 BAR4 DMA ctrl window Niklas Cassel
2026-02-25 20:23 ` Frank Li
2026-03-01 13:30 ` Koichiro Den
2026-02-25 17:03 ` [PATCH v2 4/9] PCI: endpoint: Introduce pci_epc_bar_type BAR_DISABLED Niklas Cassel
2026-02-25 20:24 ` Frank Li
2026-02-25 17:03 ` [PATCH v2 5/9] PCI: dwc: Replace certain BAR_RESERVED with BAR_DISABLED in glue drivers Niklas Cassel
2026-02-25 20:26 ` Frank Li
2026-02-25 17:03 ` [PATCH v2 6/9] PCI: dwc: Disable BARs in common code instead of in each glue driver Niklas Cassel
2026-02-25 20:27 ` Frank Li
2026-03-01 13:11 ` Koichiro Den
2026-02-25 17:03 ` [PATCH v2 7/9] PCI: endpoint: pci-epf-test: Advertise reserved BARs Niklas Cassel
2026-02-25 20:28 ` Frank Li
2026-02-25 17:03 ` [PATCH v2 8/9] misc: pci_endpoint_test: Give reserved BARs a distinct error code Niklas Cassel
2026-02-25 20:29 ` Frank Li
2026-02-25 17:03 ` [PATCH v2 9/9] selftests: pci_endpoint: Skip reserved BARs Niklas Cassel
2026-03-01 13:38 ` [PATCH v2 0/9] PCI: endpoint: Differentiate between disabled and " 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=aZ9aId4t6UWLMkFs@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=den@valinux.co.jp \
--cc=dlemoal@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmaddireddy@nvidia.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