Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Marcos Del Sol Vives <marcos@orca.pet>
Cc: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci: disable MSI on RDC PCI to PCI-E bridges
Date: Wed, 6 Aug 2025 16:23:12 -0500	[thread overview]
Message-ID: <20250806212312.GA18466@bhelgaas> (raw)
In-Reply-To: <20250705233209.721507-1-marcos@orca.pet>

On Sun, Jul 06, 2025 at 01:32:08AM +0200, Marcos Del Sol Vives wrote:
> These bridges, present on Vortex86DX3 and Vortex86EX2 SoCs, do not
> support MSIs. If enabled, interrupts generated by PCI-E devices never
> reach the processor.
> 
> I have contacted the manufacturer (DM&P) and they confirmed that PCI MSIs
> need to be disabled for them.
> 
> Signed-off-by: Marcos Del Sol Vives <marcos@orca.pet>

Applied to pci/msi for v6.18, thanks!

> ---
>  drivers/pci/quirks.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index d7f4ee634263..f610ea45ca9e 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -2715,6 +2715,7 @@ static void quirk_disable_msi(struct pci_dev *dev)
>  DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_8131_BRIDGE, quirk_disable_msi);
>  DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_VIA, 0xa238, quirk_disable_msi);
>  DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x5a3f, quirk_disable_msi);
> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_RDC, 0x1031, quirk_disable_msi);
>  
>  /*
>   * The APC bridge device in AMD 780 family northbridges has some random
> -- 
> 2.34.1
> 

      reply	other threads:[~2025-08-06 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05 23:32 [PATCH] pci: disable MSI on RDC PCI to PCI-E bridges Marcos Del Sol Vives
2025-08-06 21:23 ` Bjorn Helgaas [this message]

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=20250806212312.GA18466@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marcos@orca.pet \
    /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