[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-1d7f8900-10db-40c0-a0aa-47bb99ed84cd-1604508571909@3c-app-gmx-bs02>
Date: Wed, 4 Nov 2020 17:49:31 +0100
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Marc Zyngier <maz@...nel.org>, Ryder Lee <ryder.lee@...iatek.com>,
linux-mediatek@...ts.infradead.org,
Frank Wunderlich <linux@...web.de>,
linux-kernel@...r.kernel.org,
Matthias Brugger <matthias.bgg@...il.com>,
linux-pci@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Aw: Re: Re: [PATCH] pci: mediatek: fix warning in msi.h
> Gesendet: Dienstag, 03. November 2020 um 11:16 Uhr
> Von: "Thomas Gleixner" <tglx@...utronix.de>
> Any architecture which selects PCI_MSI_ARCH_FALLBACKS and does not have
> irqdomain support runs into:
>
> if (!d)
> bus->bus_flags |= PCI_BUS_FLAGS_NO_MSI;
>
> which in turn makes pci_msi_supported() return 0 and consequently makes
> pci_enable_msi[x]() fail.
i'm not that deep into this, but just my thoughts...you are the experts :)
checking for PCI_MSI_ARCH_FALLBACKS here does not help?
something like this:
#ifndef PCI_MSI_ARCH_FALLBACKS
if (!d)
bus->bus_flags |= PCI_BUS_FLAGS_NO_MSI;
#endif
imho pci_enable_msi[x]() does not do anything if there is no msi-support (or does not get called), so maybe check the PCI_BUS_FLAGS_NO_MSI before the call (if this is inside core) or inside the enable-function (if called from outside)....
or is this the issue marc talkes about (called before flag is set)?
regards Frank
Powered by blists - more mailing lists