From: Sandor Bodo-Merle <sbodomerle@gmail.com>
To: Ray Jui <ray.jui@broadcom.com>
Cc: "Marc Zyngier" <maz@kernel.org>, "Pali Rohár" <pali@kernel.org>,
linux-pci@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: Re: pcie-iproc-msi.c: Bug in Multi-MSI support?
Date: Wed, 26 May 2021 22:18:47 +0200 [thread overview]
Message-ID: <CABLWAfR1SFoDUWQtvSOohvT36YeDQLpJ-B40cE_4vMbWKsarFw@mail.gmail.com> (raw)
In-Reply-To: <964cc65e-5c44-8d29-9c08-013a64a5c6fd@broadcom.com>
On Wed, May 26, 2021 at 7:34 PM Ray Jui <ray.jui@broadcom.com> wrote:
>
>
> Here's the thing. All Broadcom ARMv8 based SoCs have migrated to use
> either gicv2m or gicv3-its for MSI/MSIX support. The platforms that
> still use iProc event queue based MSI are only legacy ARMv7 based
> platforms. Out of them:
>
> NSP - dual core
> Cygnus - single core
> HR2 - single core
>
> So based on this, it seems to me that it still makes sense to allow
> multi-msi to be supported on single core platforms, and Sandor's company
> seems to need such support in their particular use case. Sandor, can you
> confirm?
Right - we are using it in production on legacy ARMv7 SOCs.
>
>
> Thanks. This makes sense. And it looks like this can be addressed
> separately from the above issue. I'll have to allocate time to work on
> this. In addition, I'd also need someone else with the NSP dual-core
> platform to test it for me since we don't have these legacy platforms in
> our office anymore.
>
I will be able to test patches on the XGS Katana2 SOC - which is dual core.
prev parent reply other threads:[~2021-05-26 20:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:00 pcie-iproc-msi.c: Bug in Multi-MSI support? Pali Rohár
2021-05-20 13:47 ` Sandor Bodo-Merle
2021-05-20 14:05 ` Pali Rohár
2021-05-20 14:22 ` Sandor Bodo-Merle
2021-05-20 17:11 ` Ray Jui
2021-05-20 19:31 ` Sandor Bodo-Merle
2021-05-21 11:39 ` Sandor Bodo-Merle
2021-05-21 14:00 ` Sandor Bodo-Merle
2021-05-24 10:37 ` Marc Zyngier
2021-05-25 17:27 ` Ray Jui
2021-05-25 17:35 ` Pali Rohár
2021-05-25 17:39 ` Ray Jui
2021-05-26 7:57 ` Marc Zyngier
2021-05-26 16:10 ` Sandor Bodo-Merle
2021-06-02 8:34 ` Marc Zyngier
2021-06-03 16:59 ` Ray Jui
2021-06-04 9:17 ` Sandor Bodo-Merle
2021-06-04 16:47 ` Ray Jui
2021-05-26 17:34 ` Ray Jui
2021-05-26 20:18 ` Sandor Bodo-Merle [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=CABLWAfR1SFoDUWQtvSOohvT36YeDQLpJ-B40cE_4vMbWKsarFw@mail.gmail.com \
--to=sbodomerle@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-pci@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pali@kernel.org \
--cc=ray.jui@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.