From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: <bhelgaas@google.com>, <lpieralisi@kernel.org>,
<kwilczynski@kernel.org>, <mani@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<kishon@kernel.org>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>, <Frank.Li@nxp.com>,
<den@valinux.co.jp>, <hongxing.zhu@nxp.com>,
<jingoohan1@gmail.com>, <vidyas@nvidia.com>, <cassel@kernel.org>,
<18255117159@163.com>
Cc: <linux-pci@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>
Subject: [PATCH v2 2/5] PCI: endpoint: Allow only_64bit on BAR_RESERVED
Date: Tue, 3 Mar 2026 12:50:01 +0530 [thread overview]
Message-ID: <20260303072004.2384079-3-mmaddireddy@nvidia.com> (raw)
In-Reply-To: <20260303072004.2384079-1-mmaddireddy@nvidia.com>
Remove the documentation that forbids setting only_64bit on a BAR of
type BAR_RESERVED.
When a reserved BAR is 64-bit by default, setting only_64bit is the
most accurate description. If we later add support to disable a
reserved BAR (e.g. disable_bar() for BARs that were never set via
set_bar()), the implementation will need to clear the adjacent BAR
(upper 32 bits) as well; having only_64bit set documents that
requirement.
Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
---
v2: New patch in v2
include/linux/pci-epc.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/include/linux/pci-epc.h b/include/linux/pci-epc.h
index fb3f34829d2b..8ed000dbeca4 100644
--- a/include/linux/pci-epc.h
+++ b/include/linux/pci-epc.h
@@ -247,11 +247,6 @@ struct pci_epc_bar_rsvd_region {
* should be configured as 32-bit or 64-bit, the EPF driver must
* configure this BAR as 64-bit. Additionally, the BAR succeeding
* this BAR must be set to type BAR_64BIT_UPPER.
- *
- * only_64bit should not be set on a BAR of type BAR_RESERVED.
- * (If BARx is a 64-bit BAR that an EPF driver is not allowed to
- * reprogram, 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
*/
--
2.34.1
next prev parent reply other threads:[~2026-03-03 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 7:19 [PATCH v2 0/5] PCI: endpoint: Add Tegra194/234 BAR layout and pci_endpoint_test support Manikanta Maddireddy
2026-03-03 7:20 ` [PATCH v2 1/5] PCI: endpoint: Add reserved region type for MSI-X Table and PBA Manikanta Maddireddy
2026-03-03 13:46 ` Niklas Cassel
2026-03-03 7:20 ` Manikanta Maddireddy [this message]
2026-03-03 13:46 ` [PATCH v2 2/5] PCI: endpoint: Allow only_64bit on BAR_RESERVED Niklas Cassel
2026-03-03 7:20 ` [PATCH v2 3/5] PCI: tegra194: Make BAR0 programmable and remove 1MB size limit Manikanta Maddireddy
2026-03-03 13:48 ` Niklas Cassel
2026-03-03 7:20 ` [PATCH v2 4/5] PCI: tegra194: Expose BAR2 (MSI-X) and BAR4 (DMA) as 64-bit BAR_RESERVED Manikanta Maddireddy
2026-03-03 13:51 ` Niklas Cassel
2026-03-03 7:20 ` [PATCH v2 5/5] misc: pci_endpoint_test: Add Tegra194 and Tegra234 device table entries Manikanta Maddireddy
2026-03-03 13:49 ` Niklas Cassel
2026-03-21 12:32 ` [PATCH v2 0/5] PCI: endpoint: Add Tegra194/234 BAR layout and pci_endpoint_test support Manivannan Sadhasivam
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=20260303072004.2384079-3-mmaddireddy@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=18255117159@163.com \
--cc=Frank.Li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=den@valinux.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@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