diff options
| author | Jerome Brunet <[email protected]> | 2025-06-03 17:03:40 +0000 |
|---|---|---|
| committer | Manivannan Sadhasivam <[email protected]> | 2025-07-09 12:36:51 +0000 |
| commit | e7cd58d2fdf8b3d2cb8c1d7a6d8eac2c67e5e18b (patch) | |
| tree | d48802a5356efdd636fe5306035ca2b071cea5b5 /drivers/pci/controller/dwc/pci-keystone.c | |
| parent | PCI: endpoint: pci-epf-vntb: Align MW naming with config names (diff) | |
| download | kernel-e7cd58d2fdf8b3d2cb8c1d7a6d8eac2c67e5e18b.tar.gz kernel-e7cd58d2fdf8b3d2cb8c1d7a6d8eac2c67e5e18b.zip | |
PCI: endpoint: pci-epf-vntb: Allow BAR assignment via configfs
The current BAR configuration for the PCI vNTB endpoint function allocates
BARs in order, which lacks flexibility and does not account for
platform-specific quirks. This is problematic on Renesas platforms, where
BAR_4 is a fixed 256B region that ends up being used for MW1, despite being
better suited for doorbells.
Add new configfs attributes to allow users to specify arbitrary BAR
assignments. If no configuration is provided, the driver retains its
original behavior of sequential BAR allocation, preserving compatibility
with existing userspace setups.
This enables use cases such as assigning BAR_2 for MW1 and using the
limited BAR_4 for doorbells on Renesas platforms.
Signed-off-by: Jerome Brunet <[email protected]>
[mani: adjusted the indent of EPF_NTB_BAR_W, fixed kdoc & squashed bar fix]
Signed-off-by: Manivannan Sadhasivam <[email protected]>
Reviewed-by: Frank Li <[email protected]>
Link: https://patch.msgid.link/[email protected]
Diffstat (limited to 'drivers/pci/controller/dwc/pci-keystone.c')
0 files changed, 0 insertions, 0 deletions