On 10/28/20, 4:47 PM, Rob Herring wrote: > > There are 3 possible MSI implementations for the DWC host. The first is > using the built-in DWC MSI controller. The 2nd is a custom MSI > controller as part of the PCI host (keystone only). The 3rd is an > external MSI controller (typically GICv3 ITS). Currently, the last 2 > are distinguished with a .msi_host_init() hook with the 3rd option using > an empty function. However we can detect the 3rd case with the presence > of 'msi-parent' or 'msi-map' properties, so let's do that instead and > remove the empty functions. > > Cc: Murali Karicheri <[email protected]> > Cc: Lorenzo Pieralisi <[email protected]> > Cc: Bjorn Helgaas <[email protected]> > Cc: Minghuan Lian <[email protected]> > Cc: Mingkai Hu <[email protected]> > Cc: Roy Zang <[email protected]> > Cc: Jingoo Han <[email protected]>
Acked-by: Jingoo Han <[email protected]> Best regards, Jingoo Han > Cc: Gustavo Pimentel <[email protected]> > Cc: [email protected] > Signed-off-by: Rob Herring <[email protected]> > --- > drivers/pci/controller/dwc/pci-keystone.c | 9 ------- > drivers/pci/controller/dwc/pci-layerscape.c | 25 ------------------- > .../pci/controller/dwc/pcie-designware-host.c | 20 +++++++++------ > drivers/pci/controller/dwc/pcie-designware.h | 1 + > drivers/pci/controller/dwc/pcie-intel-gw.c | 9 ------- > 5 files changed, 13 insertions(+), 51 deletions(-) [...]
