From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Johannes Thumshirn <johannes.thumshirn@men.de>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, 'David Engster' <david.engster@mahr.de>
Subject: Re: FSL MSI Mapping
Date: Fri, 31 Oct 2014 12:28:20 +0100 [thread overview]
Message-ID: <54537254.5050401@linutronix.de> (raw)
In-Reply-To: <20141031081225.GA20831@jtlinux>
On 10/31/2014 09:12 AM, Johannes Thumshirn wrote:
> On Thu, Oct 30, 2014 at 02:51:57PM +1100, Michael Ellerman wrote:
>> Why would you not use MSI-X ?
If I'm not mistaken, a PCI-E requirement is to support MSI but MSI-X is
optional. And with MSI you can have multiple interrupts per single
device (power of two, max 32).
Now imagine you have a FPGA with two (or more) different devices in it
and you don't want them to share the IRQ line (for $reason). I bet the
HW developer sees MSI and MSI-X and the former is for some reason
cheaper compared to MSI-X and it fits the needs. So…
>
> Does anyone (especially the original author) have any objections if I re-spin
> the patch series?
I didn't get around to address the review comments so it did not went
in and there was no v2. Feel free re-do the series.
Sebastian
prev parent reply other threads:[~2014-10-31 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:06 FSL MSI Mapping Johannes Thumshirn
2014-10-28 19:10 ` Scott Wood
2014-10-29 6:54 ` Johannes Thumshirn
2014-11-03 21:57 ` Scott Wood
2014-10-30 3:51 ` Michael Ellerman
2014-10-30 6:58 ` Johannes Thumshirn
2014-10-31 8:12 ` Johannes Thumshirn
2014-10-31 11:28 ` Sebastian Andrzej Siewior [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=54537254.5050401@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=david.engster@mahr.de \
--cc=johannes.thumshirn@men.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).