qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Francisco Iglesias <frasse.iglesias@gmail.com>
To: peter.maydell@linaro.org
Cc: Kinsey Moore <kinsey.moore@oarcorp.com>,
	qemu-devel@nongnu.org, philmd@linaro.org
Subject: Re: [PATCH v2] hw/arm/xlnx: Connect secondary CGEM IRQs
Date: Mon, 10 Jul 2023 16:09:49 +0200	[thread overview]
Message-ID: <20230710140948.GJ6984@fralle-msi> (raw)
In-Reply-To: <e36a681f-53e2-8379-078e-25e43fc3966e@linaro.org>


+PMM (I think this one might have fallen throught the cracks)

Best regards,
Francisco Iglesias

On [2023 Jun 18] Sun 00:50:47, Philippe Mathieu-Daudé wrote:
> On 16/6/23 16:38, Kinsey Moore wrote:
> > The Cadence GEM peripherals as configured for Zynq MPSoC and Versal
> > platforms have two priority queues with separate interrupt sources for
> > each. If the interrupt source for the second priority queue is not
> > connected, they work in polling mode only. This change connects the
> > second interrupt source for platforms where it is available. This patch
> > has been tested using the lwIP stack with a Xilinx-supplied driver from
> > their embeddedsw repository.
> > 
> > Signed-off-by: Kinsey Moore <kinsey.moore@oarcorp.com>
> > ---
> >   hw/arm/xlnx-versal.c         | 12 +++++++++++-
> >   hw/arm/xlnx-zynqmp.c         | 11 ++++++++++-
> >   include/hw/arm/xlnx-versal.h |  1 +
> >   include/hw/arm/xlnx-zynqmp.h |  1 +
> >   4 files changed, 23 insertions(+), 2 deletions(-)
> 
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> 
> 


  reply	other threads:[~2023-07-10 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 14:38 [PATCH v2] hw/arm/xlnx: Connect secondary CGEM IRQs Kinsey Moore
2023-06-16 20:25 ` Francisco Iglesias
2023-06-17 22:50 ` Philippe Mathieu-Daudé
2023-07-10 14:09   ` Francisco Iglesias [this message]
2024-09-25 19:34     ` Kinsey Moore
2024-09-27 16:48       ` Peter Maydell

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=20230710140948.GJ6984@fralle-msi \
    --to=frasse.iglesias@gmail.com \
    --cc=kinsey.moore@oarcorp.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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).