diff options
author | Niklas Cassel <cassel@kernel.org> | 2024-02-16 16:45:14 +0300 |
---|---|---|
committer | Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> | 2024-02-16 18:00:46 +0300 |
commit | e01c9797c0ebb307c9bb196c677f6e571335773e (patch) | |
tree | edfb2244165f0cddeb12665e3c3ebf5db6b9b40f /drivers/pci/hotplug/pci_hotplug_core.c | |
parent | c670e29f5bfe6c404a5405a0fa8e235de2f4f0c9 (diff) | |
download | linux-e01c9797c0ebb307c9bb196c677f6e571335773e.tar.xz |
PCI: endpoint: Clean up hardware description for BARs
The hardware description for BARs is scattered in many different variables
in pci_epc_features. Some of these things are mutually exclusive, so it
can create confusion over which variable that has precedence over another.
Improve the situation by creating a struct pci_epc_bar_desc, and a new
enum pci_epc_bar_type, and convert the endpoint controller drivers to use
this more well defined format.
Additionally, some endpoint controller drivers mark the BAR succeeding a
"64-bit only BAR" as reserved, while some do not. By definition, a 64-bit
BAR uses the succeeding BAR for the upper 32-bits, so an EPF driver cannot
use a BAR succeeding a 64-bit BAR. Ensure that all endpoint controller
drivers are uniform, and actually describe a reserved BAR as reserved.
Signed-off-by: Niklas Cassel <cassel@kernel.org>
Reviewed-by: Kishon Vijay Abraham I <kishon@kernel.org>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Link: https://lore.kernel.org/r/20240216134524.1142149-2-cassel@kernel.org
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Diffstat (limited to 'drivers/pci/hotplug/pci_hotplug_core.c')
0 files changed, 0 insertions, 0 deletions