From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-pci@vger.kernel.org
Subject: Could enabling MSI interrupts lead to problems?
Date: Mon, 2 Dec 2013 14:43:49 +0100 [thread overview]
Message-ID: <20131202134349.GA19436@linutronix.de> (raw)
I've been playing with PCIe parallel port cards. Both of them have the
MSI flag set and it is possible to enable MSI interrupts. The advantage
is that the interrupt is no longer shared with other devices and it
becomes edge instead of level.
Now I'm thinking about posting a patch which always calls
pci_enable_msi() on init so we have MSI support in parport_pc driver if
possible. I know that atleast XHCI has a flag not to enable MSI on some
FRESCO_LOGIC devices because they announce it but can't generate
interrupts with MSI enabled. Is this something "usual" and I should only
enable MSI based on a whitelist or is this more something exceptional?
Sebastian
reply other threads:[~2013-12-02 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131202134349.GA19436@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-pci@vger.kernel.org \
/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).