From: Marc Zyngier <marc.zyngier@arm.com>
To: Ray Jui <rjui@broadcom.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Hauke Mehrtens <hauke@hauke-m.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 4/5] PCI: iproc: Add iProc PCIe MSI support
Date: Fri, 04 Dec 2015 18:01:42 +0000 [thread overview]
Message-ID: <5661D506.6000509@arm.com> (raw)
In-Reply-To: <1449250502-10679-5-git-send-email-rjui@broadcom.com>
On 04/12/15 17:35, Ray Jui wrote:
> This patch adds PCIe MSI support for both PAXB and PAXC interfaces on
> all iProc based platforms
>
> The iProc PCIe MSI support deploys an event queue based implementation.
> Each event queue is serviced by a GIC interrupt and can support up to 64
> MSI vectors. Host memory is allocated for the event queues, and each event
> queue consists of 64 word-sized entries. MSI data is written to the
> lower 16-bit of each entry, whereas the upper 16-bit of the entry is
> reserved for the controller for internal processing
>
> Each event queue is tracked by a head pointer and tail pointer. Head
> pointer indicates the next entry in the event queue to be processed by
> the driver and is updated by the driver after processing is done.
> The controller uses the tail pointer as the next MSI data insertion
> point. The controller ensures MSI data is flushed to host memory before
> updating the tail pointer and then triggering the interrupt
>
> MSI IRQ affinity is supported by evenly distributing the interrupts to
> each CPU core. MSI vector is moved from one GIC interrupt to another in
> order to steer to the target CPU
>
> Therefore, the actual number of supported MSI vectors is:
>
> M * 64 / N
>
> where M denotes the number of GIC interrupts (event queues), and N
> denotes the number of CPU cores
>
> This iProc event queue based MSI support should not be used with newer
> platforms with integrated MSI support in the GIC (e.g., giv2m or
> gicv3-its)
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Reviewed-by: Anup Patel <anup.patel@broadcom.com>
> Reviewed-by: Vikram Prakash <vikramp@broadcom.com>
> Reviewed-by: Scott Branden <sbranden@broadcom.com>
Good thing I didn't reply on v4!
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-12-04 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:34 [PATCH v5 0/5] Add iProc PCIe PAXC and MSI support Ray Jui
2015-12-04 17:34 ` [PATCH v5 1/5] PCI: iproc: Update iProc PCIe device tree binding Ray Jui
2015-12-04 17:34 ` [PATCH v5 2/5] PCI: iproc: Add PAXC interface support Ray Jui
2015-12-04 17:35 ` [PATCH v5 3/5] PCI: iproc: Add iProc PCIe MSI device tree binding Ray Jui
2015-12-04 17:35 ` [PATCH v5 4/5] PCI: iproc: Add iProc PCIe MSI support Ray Jui
2015-12-04 18:01 ` Marc Zyngier [this message]
2015-12-04 17:35 ` [PATCH v5 5/5] ARM: dts: Enable MSI support for Broadcom Cygnus Ray Jui
2015-12-07 22:15 ` Florian Fainelli
2015-12-07 17:01 ` [PATCH v5 0/5] Add iProc PCIe PAXC and MSI support Bjorn Helgaas
2015-12-07 20:32 ` Florian Fainelli
2015-12-07 21:33 ` Bjorn Helgaas
2015-12-07 22:15 ` Florian Fainelli
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=5661D506.6000509@arm.com \
--to=marc.zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjui@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.