> Hi Bharat,
>> > Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP.
> >
> > +/* SSPL ERROR */
> > +#define SLVERR 0x02
> > +#define DECERR 0x03
> > +
> > +struct nwl_msi { /* struct nwl_msi - MSI information
> */
> > + struct msi_controller chip; /* chip: MSI controller */
>
> We're moving away from msi_controller altogether, as the kernel now has all
> the necessary infrastructure to do this properly.
>
> Please convert this driver to msi domains (see drivers/pci/host/pci-xgene-
> msi.c or the gic-v2m driver as examples of how this is being done).
As suggested I have gone through the code in pci-gene-msi.c for msi domains,
and have gone through IRQ Domain documentation.
I mainly observe when we have more than one interrupt controller involved
between device and cpu we use "Hierarchy IRQ domain" (parent and child msi
domains). But in our case we
don't have any such Hierarchy and we have single interrupt controller.
In such case is it necessary to use multiple domains in software which actually
isn't case in hardware.
Thanks
Bharat
>
> > + DECLARE_BITMAP(used, INT_PCI_MSI_NR); /* used: Declare
> Bitmap
> > + for MSI */
> > + struct irq_domain *domain; /* domain: IRQ domain pointer */
> > + unsigned long pages; /* pages: MSI pages */
>
> Overall, I think it would make sense to split the PCIe controller driver and
> the
> MSI controller (in separate files as well).
>
> Please keep me posted on the updates.
>
> Thanks,
>
> M.
> --
> Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
