u-boot.git/drivers/pci, branch v2021.10

pci: Drop DM_PCI

2021-09-13T22:23:13Z

This option has not effect now. Drop it, using PCI instead where needed. Signed-off-by: Simon Glass

pci: Drop PCI_INDIRECT_BRIDGE

2021-09-13T22:23:13Z

This does not work with driver model so can be removed. Signed-off-by: Simon Glass

arm: a37xx: pci: Don't spam about PIO Response Status

2021-09-10T07:01:51Z

Use dev_dbg() instead of dev_err() in pcie_advk_check_pio_status(). For example CRS is not an error status, it just says that the request should be retried. Without this, U-Boot spams the terminal with pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x100000 pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x108000 pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x110000 pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x120000 pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x128000 pcie_advk pcie@d0070000: Non-posted PIO Response Status: UR, 0xc80 @ 0x130000 ... when a device is not connected to a PCIe switch (Unsupported Request from the switch). Signed-off-by: Marek Behún Reviewed-by: Pali Rohár Reviewed-by: Stefan Roese

arm: a37xx: pci: Implement re-issuing config requests on CRS response

2021-09-10T07:01:51Z

According to PCIe base specification, if CRS Software Visibility is not enabled, the Root Complex must re-issue the Configuration Request as a new Request. Normally this part of Root Complex is implemented in hardware but aardvark is somehow special and does not implement it in hardware and expect that handling of config requests are fully implemented in software. This re-issuing functionality is required also because U-Boot does not support CRS Software Visibility feature and therefore expects that Root Complex re-issues requests as is specified in PCIe base specification. Retry / re-issue config request up to the PIO_MAX_RETRIES, to prevent infinite loop. After retry count exceed PIO_MAX_RETRIES, returns failure. Signed-off-by: Pali Rohár Reviewed-by: Stefan Roese

arm: a37xx: pci: Disable returning CRS response

2021-09-10T07:01:51Z

There was mistake in commit 4cd61c43fd51 ("arm: a37xx: pci: Fix handling PIO config error responses"). U-Boot does not support handling of CRS return value for PCI_VENDOR_ID config read request and also does not set CRSSVE bit. Therefore disable returning CRS response for now. Signed-off-by: Pali Rohár Fixes: 4cd61c43fd51 ("arm: a37xx: pci: Fix handling PIO config error responses") Reviewed-by: Stefan Roese

arm: a37xx: pci: Fix handling PIO config error responses

2021-08-11T06:42:26Z

Returning fabricated CRS value (0xFFFF0001) by PCIe Root Complex to OS is allowed only for 4-byte PCI_VENDOR_ID config read request and only when CRSSVE bit in Root Port PCIe device is enabled. In all other error PCIe Root Complex must return all-ones. So implement this logic in pci-aardvark.c driver properly. aardvark HW does not have Root Port PCIe device and U-Boot does not implement emulation of this device. So expect that CRSSVE bit is set as U-Boot can already handle CRS value for PCI_VENDOR_ID config read request. More callers of pci_bus_read_config() function in U-Boot do not check for return value, but check readback value. Therefore always fill readback value in pcie_advk_read_config() function. On error fill all-ones of correct size as it is required for PCIe Root Complex. And also correctly propagates error from failed config write request to return value of pcie_advk_write_config() function. Most U-Boot callers ignores this return value, but it is a good idea to return correct value from function. These issues about return value of failed config read requests, including special handling of CRS were reported by Lorenzo and Bjorn for Linux kernel driver pci-aardvark together with quotes from PCIe r4.0 spec, see details: https://lore.kernel.org/linux-pci/20210624213345.3617-1-pali@kernel.org/t/#u Signed-off-by: Pali Rohár Reviewed-by: Stefan Roese

pci: ppc: Drop ftpci100 driver

2021-08-06T12:26:48Z

This is not used in U-Boot at present. Drop it and related config options. Signed-off-by: Simon Glass

pci: imx: Drop use of DM_PCI

2021-08-05T23:46:35Z

Now that DM_PCI is always enabled we don't need to check it. Drop this old code. Signed-off-by: Simon Glass

pci: msc01: Drop use of DM_PCI

2021-08-05T23:46:35Z

Now that DM_PCI is always enabled we don't need to check it. Drop this old code. Signed-off-by: Simon Glass

pci: gt64120: Drop use of DM_PCI

2021-08-05T23:46:35Z

Now that DM_PCI is always enabled we don't need to check it. Drop this old code. Signed-off-by: Simon Glass