Forked from
drm / msm
Source project has a limited visibility.
-
Eric Auger authored
Currently acpi_viot_init() gets called after the pci device has been scanned and pci_enable_acs() has been called. So pci_request_acs() fails to be taken into account leading to wrong single iommu group topologies when dealing with multi-function root ports for instance. We cannot simply move the acpi_viot_init() earlier, similarly as the IORT init because the VIOT parsing relies on the pci scan. However we can detect VIOT is present earlier and in such a case, request ACS. Introduce a new acpi_viot_early_init() routine that allows to call pci_request_acs() before the scan. While at it, guard the call to pci_request_acs() with #ifdef CONFIG_PCI. Fixes: 3cf48554 ("ACPI: Add driver for the VIOT table") Signed-off-by:
Eric Auger <eric.auger@redhat.com> Reported-by:
Jin Liu <jinl@redhat.com> Reviewed-by:
Jean-Philippe Brucker <jean-philippe@linaro.org> Tested-by:
Jean-Philippe Brucker <jean-philippe@linaro.org> Signed-off-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Eric Auger authoredCurrently acpi_viot_init() gets called after the pci device has been scanned and pci_enable_acs() has been called. So pci_request_acs() fails to be taken into account leading to wrong single iommu group topologies when dealing with multi-function root ports for instance. We cannot simply move the acpi_viot_init() earlier, similarly as the IORT init because the VIOT parsing relies on the pci scan. However we can detect VIOT is present earlier and in such a case, request ACS. Introduce a new acpi_viot_early_init() routine that allows to call pci_request_acs() before the scan. While at it, guard the call to pci_request_acs() with #ifdef CONFIG_PCI. Fixes: 3cf48554 ("ACPI: Add driver for the VIOT table") Signed-off-by:
Eric Auger <eric.auger@redhat.com> Reported-by:
Jin Liu <jinl@redhat.com> Reviewed-by:
Jean-Philippe Brucker <jean-philippe@linaro.org> Tested-by:
Jean-Philippe Brucker <jean-philippe@linaro.org> Signed-off-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com>