From: Marc Zyngier <maz@kernel.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: bhelgaas@google.com, lorenzo.pieralisi@arm.com,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/MSI: Fix MSIs for generic hosts that use device-tree's "msi-map"
Date: Tue, 18 May 2021 09:48:06 +0100 [thread overview]
Message-ID: <87bl98v35l.wl-maz@kernel.org> (raw)
In-Reply-To: <YJqQuKZOeorJ+/Py@myrica>
On Tue, 11 May 2021 15:12:08 +0100,
Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
>
> Hi Marc,
>
> On Mon, May 10, 2021 at 07:23:14PM +0100, Marc Zyngier wrote:
> > > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > > index 3a62d09b8869..275204646c68 100644
> > > --- a/drivers/pci/probe.c
> > > +++ b/drivers/pci/probe.c
> > > @@ -925,7 +925,8 @@ static int pci_register_host_bridge(struct pci_host_bridge *bridge)
> > > device_enable_async_suspend(bus->bridge);
> > > pci_set_bus_of_node(bus);
> > > pci_set_bus_msi_domain(bus);
> > > - if (bridge->msi_domain && !dev_get_msi_domain(&bus->dev))
> > > + if (bridge->msi_domain && !dev_get_msi_domain(&bus->dev) &&
> > > + !pci_host_of_has_msi_map(parent))
> > > bus->bus_flags |= PCI_BUS_FLAGS_NO_MSI;
> > >
> > > if (!parent)
> >
> > Do we need something similar for IORT, which implements a similar
> > functionality to "msi-map"? My ACPI boxes seem to get their MSIs just
> > fine though...
>
> I'm not seeing the issue either under ACPI on the fast model, because it
> doesn't go through pci_host_common_probe(), and bridge->msi_domain is not
> set:
>
> acpi_pci_root_add()
> pci_acpi_scan_root()
> acpi_pci_root_create()
> pci_create_root_bus()
> pci_register_host_bridge()
>
> It doesn't look like any ACPI platform can set bridge->msi_domain at the
> moment. If they do flip the switch at some point, MSIs won't work and
> we'll need something for IORT. But I'd leave it out for the moment.
Fair enough, although there seem to be the opposite issue on some
platforms that do not have any MSI to offer (see [1]). I guess we'll
cross that bridge eventually.
For this patch:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
[1] https://lore.kernel.org/r/b5a5a6d8-6ffc-8c5c-c5b1-fb4f5616069f@arm.com
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-05-18 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 17:31 [PATCH] PCI/MSI: Fix MSIs for generic hosts that use device-tree's "msi-map" Jean-Philippe Brucker
2021-05-10 18:23 ` Marc Zyngier
2021-05-11 14:12 ` Jean-Philippe Brucker
2021-05-18 8:48 ` Marc Zyngier [this message]
2021-05-25 23:40 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl98v35l.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bhelgaas@google.com \
--cc=jean-philippe@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).