From: Marc Zyngier <maz@kernel.org>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rui Salvaterra <rsalvaterra@gmail.com>,
kernel-team@android.com
Subject: [PATCH 0/2] PCI: MSI: Deal with devices lying about their masking capability
Date: Thu, 4 Nov 2021 18:01:28 +0000 [thread overview]
Message-ID: <20211104180130.3825416-1-maz@kernel.org> (raw)
Rui reported[1] that his Nvidia ION system stopped working with 5.15,
with the AHCI device failing to get any MSI. A rapid investigation
revealed that although the device doesn't advertise MSI masking, it
actually needs it. Quality hardware indeed.
Anyway, the couple of patches below are an attempt at dealing with the
issue in a more or less generic way.
[1] https://lore.kernel.org/r/CALjTZvbzYfBuLB+H=fj2J+9=DxjQ2Uqcy0if_PvmJ-nU-qEgkg@mail.gmail.com
Marc Zyngier (2):
PCI: MSI: Deal with devices lying about their MSI mask capability
PCI: Add MSI masking quirk for Nvidia ION AHCI
drivers/pci/msi.c | 3 +++
drivers/pci/quirks.c | 6 ++++++
include/linux/pci.h | 2 ++
3 files changed, 11 insertions(+)
--
2.30.2
next reply other threads:[~2021-11-04 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 18:01 Marc Zyngier [this message]
2021-11-04 18:01 ` [PATCH 1/2] PCI: MSI: Deal with devices lying about their MSI mask capability Marc Zyngier
2021-11-11 8:57 ` [tip: irq/urgent] PCI/MSI: " tip-bot2 for Marc Zyngier
2021-11-04 18:01 ` [PATCH 2/2] PCI: Add MSI masking quirk for Nvidia ION AHCI Marc Zyngier
2021-11-05 13:14 ` [PATCH 0/2] PCI: MSI: Deal with devices lying about their masking capability Thomas Gleixner
2021-11-16 10:21 ` Rui Salvaterra
2021-11-16 10:39 ` Greg KH
2021-11-16 10:47 ` Rui Salvaterra
2021-11-16 10:56 ` Greg KH
2021-11-19 14:05 ` Greg KH
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=20211104180130.3825416-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=bhelgaas@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rsalvaterra@gmail.com \
--cc=tglx@linutronix.de \
/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).