summaryrefslogtreecommitdiff
path: root/kernel
diff options
context:
space:
mode:
authorWei Chen <Wei.Chen@arm.com>2016-06-13 09:20:17 (GMT)
committerWill Deacon <will.deacon@arm.com>2016-07-01 13:04:36 (GMT)
commit112c898b59dd5cfd95ee30dfe7cc4fc11a6d484e (patch)
treea278cb60267b95efc989ac87c7348e487d6cbd36 /kernel
parent560829b4f6c34adae82082fe86d21e7c6cdc4eaf (diff)
downloadlinux-112c898b59dd5cfd95ee30dfe7cc4fc11a6d484e.tar.xz
iommu/arm-smmu: request pcie devices to enable ACS
The PCIe ACS capability will affect the layout of iommu groups. Generally speaking, if the path from root port to the PCIe device is ACS enabled, the iommu will create a single iommu group for this PCIe device. If all PCIe devices on the path are ACS enabled then Linux can determine this path is ACS enabled. Linux use two PCIe configuration registers to determine the ACS status of PCIe devices: ACS Capability Register and ACS Control Register. The first register is used to check the implementation of ACS function of a PCIe device, the second register is used to check the enable status of ACS function. If one PCIe device has implemented and enabled the ACS function then Linux will determine this PCIe device enabled ACS. From the Chapter:6.12 of PCI Express Base Specification Revision 3.1a, we can find that when a PCIe device implements ACS function, the enable status is set to disabled by default and can be enabled by ACS-aware software. ACS will affect the iommu groups topology, so, the iommu driver is ACS-aware software. This patch adds a call to pci_request_acs() to the arm-smmu driver to enable the ACS function in PCIe devices that support it, when they get probed. Reviewed-by: Robin Murphy <robin.murphy@arm.com> Reviewed-by: Eric Auger <eric.auger@redhat.com> Signed-off-by: Wei Chen <Wei.Chen@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions