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 <m-kariche...@ti.com> > Cc: Lorenzo Pieralisi <lorenzo.pieral...@arm.com> > Cc: Bjorn Helgaas <bhelg...@google.com> > Cc: Minghuan Lian <minghuan.l...@nxp.com> > Cc: Mingkai Hu <mingkai...@nxp.com> > Cc: Roy Zang <roy.z...@nxp.com> > Cc: Jingoo Han <jingooh...@gmail.com>
Acked-by: Jingoo Han <jingooh...@gmail.com> Best regards, Jingoo Han > Cc: Gustavo Pimentel <gustavo.pimen...@synopsys.com> > Cc: linuxppc-dev@lists.ozlabs.org > Signed-off-by: Rob Herring <r...@kernel.org> > --- > 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(-) [...]
