PCI: iproc: Fix up corrupted PAXC root complex config registers
On certain versions of Broadcom PAXC based root complexes, certain regions of the configuration space are corrupted. As a result, it prevents the Linux PCIe stack from traversing the linked list of the capability registers completely and therefore the root complex is not advertised as "PCIe capable". This prevents the correct PCIe RID from being parsed in the kernel PCIe stack. A correct RID is required for mapping to a stream ID from the SMMU or the device ID from the GICv3 ITS. This patch fixes up the issue by manually populating the related PCIe capabilities. Signed-off-by: Ray Jui <rjui@broadcom.com> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Reviewed-by: Oza Pawandeep <poza@codeaurora.org>
This commit is contained in:

committed by
Lorenzo Pieralisi

parent
b95e2cd021
commit
3bc70825e4
@@ -60,6 +60,8 @@ struct iproc_msi;
|
||||
* @ep_is_internal: indicates an internal emulated endpoint device is connected
|
||||
* @has_apb_err_disable: indicates the controller can be configured to prevent
|
||||
* unsupported request from being forwarded as an APB bus error
|
||||
* @fix_paxc_cap: indicates the controller has corrupted capability list in its
|
||||
* config space registers and requires SW based fixup
|
||||
*
|
||||
* @need_ob_cfg: indicates SW needs to configure the outbound mapping window
|
||||
* @ob: outbound mapping related parameters
|
||||
@@ -85,6 +87,7 @@ struct iproc_pcie {
|
||||
int (*map_irq)(const struct pci_dev *, u8, u8);
|
||||
bool ep_is_internal;
|
||||
bool has_apb_err_disable;
|
||||
bool fix_paxc_cap;
|
||||
|
||||
bool need_ob_cfg;
|
||||
struct iproc_pcie_ob ob;
|
||||
|
Reference in New Issue
Block a user