On Thu, Nov 24 2022 at 00:50, Frank Li wrote: > ┌────────────┐ ┌───────────────────────────────────┐ ┌────────────────┐ > │ │ │ │ │ │ > │ │ │ PCI Endpoint │ │ PCI Host │ > │ │ │ │ │ │ > │ │◄──┤ 1.platform_msi_domain_alloc_irqs()│ │ │ > │ │ │ │ │ │ > │ MSI ├──►│ 2.write_msi_msg() ├──►├─BAR<n> │ > │ Controller │ │ update doorbell register address│ │ │ > │ │ │ for BAR │ │ │ > │ │ │ │ │ 3. Write BAR<n>│ > │ │◄──┼───────────────────────────────────┼───┤ │ > │ │ │ │ │ │ > │ ├──►│ 4.Irq Handle │ │ │ > │ │ │ │ │ │ > │ │ │ │ │ │ > └────────────┘ └───────────────────────────────────┘ └────────────────┘ > > Using platform MSI interrupt controller as endpoint(EP)'s doorbell. Can you please explain what the MSI controller is in this picture? MSI controller is not a term which is common in the interrupt handling landscape despite the fact that it's pretty wide spread in device tree bindings presumably through intensive copy & pasta cargo cult. > Basic working follow as > 1. EP function driver call platform_msi_domain_alloc_irqs() alloc a > MSI irq from MSI controller with call back function write_msi_msg(); > 2. write_msg_msg will config BAR and map to address defined in msi_msg; > 3. Host side trigger an IRQ at Endpoint by write to BAR region. You're explaining what the code does, but fail to explain the underlying mechanisms. Platform MSI is definitely the wrong mechanism here. Why? This is about a PCIe endpoint, which is usually handled by a PCI/MSI interrupt domain. Obviously this usage does not fit into the way how the "global" PCI/MSI domains work. There is upcoming work and at least the generic parts should show up in 6.2 which addresses exactly the problem you are trying to solve: https://lore.kernel.org/all/20221124225331.464480443@xxxxxxxxxxxxx https://lore.kernel.org/all/20221124230505.073418677@xxxxxxxxxxxxx plus the prove that the platform MSI mess can be replaced by this: https://lore.kernel.org/all/20221121135653.208611233@xxxxxxxxxxxxx NTB in it's current form should never have happened, but that's water down the bridge. What you really want is: 1) Convert your platform to the new MSI parent model 2) Utilize PCI/IMS which is giving you exactly what you need with proper PCI semantics Thanks, tglx
