diff options
| author | Niklas Cassel <cassel@kernel.org> | 2026-03-12 14:02:29 +0100 |
|---|---|---|
| committer | Manivannan Sadhasivam <mani@kernel.org> | 2026-03-15 22:04:22 +0530 |
| commit | 0834d6f4abd0ca35b5706d267a6e4b78303a95de (patch) | |
| tree | a5e5a6e096e69e19d2aa913064ffe3d58948540e /tools/lib/python/kdoc | |
| parent | 0b74f7d72399d4c4422ed3d68ef28b3612f71e74 (diff) | |
PCI: endpoint: Do not mark the BAR succeeding a 64-bit BAR as BAR_RESERVED
A BAR that can only be configured as a 64-bit BAR by an EPC driver is
marked as such using the "only_64bit" flag.
Currently, the documentation says that an EPC driver should explicitly
mark the BAR succeeding an "only_64bit" BAR as BAR_RESERVED.
However, a 64-bit BAR will always take up two BARs. It is thus redundant
to mark both BARs.
pci_epc_get_next_free_bar() already skips the BAR succeeding a "only_64bit"
BAR, regardless if the succeeding BAR is marked as BAR_RESERVED or not.
Thus, drop the BAR_RESERVED for a BAR succeeding a "only_64bit" BAR.
No functional changes.
Suggested-by: Manivannan Sadhasivam <mani@kernel.org>
Signed-off-by: Niklas Cassel <cassel@kernel.org>
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
Link: https://patch.msgid.link/20260312130229.2282001-13-cassel@kernel.org
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions
