From: Andrew Jones <drjones@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, peter.maydell@linaro.org,
alex.williamson@redhat.com, qemu-arm@nongnu.org,
qemu-devel@nongnu.org, wei@redhat.com, agraf@suse.de,
christoffer.dall@linaro.org, pranavkumar@linaro.org
Subject: Re: [Qemu-devel] [PATCH RESEND v3 1/3] hw/pci-host/gpex: Set INTx index/gsi mapping
Date: Mon, 11 Sep 2017 14:41:54 +0200 [thread overview]
Message-ID: <20170911124154.lpckigdp32kfiisd@hawk.localdomain> (raw)
In-Reply-To: <1499634139-20399-2-git-send-email-eric.auger@redhat.com>
On Sun, Jul 09, 2017 at 11:02:17PM +0200, Eric Auger wrote:
> From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
>
> To implement INTx to gsi routing we need to pass the gpex host
> bridge the gsi associated to each INTx index. Let's introduce
> irq_num array and gpex_set_irq_num setter function.
>
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> Signed-off-by: Tushar Jagad <tushar.jagad@linaro.org>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> ---
> hw/pci-host/gpex.c | 10 ++++++++++
> include/hw/pci-host/gpex.h | 3 +++
> 2 files changed, 13 insertions(+)
>
> diff --git a/hw/pci-host/gpex.c b/hw/pci-host/gpex.c
> index 83084b9..0d42ac2 100644
> --- a/hw/pci-host/gpex.c
> +++ b/hw/pci-host/gpex.c
> @@ -43,6 +43,16 @@ static void gpex_set_irq(void *opaque, int irq_num, int level)
> qemu_set_irq(s->irq[irq_num], level);
> }
>
> +int gpex_set_irq_num(GPEXHost *s, int index, uint32_t gsi)
> +{
> + if (index >= GPEX_NUM_IRQS) {
^extra space
> + return -EINVAL;
> + }
> +
> + s->irq_num[index] = gsi;
> + return 0;
> +}
> +
> static void gpex_host_realize(DeviceState *dev, Error **errp)
> {
> PCIHostState *pci = PCI_HOST_BRIDGE(dev);
> diff --git a/include/hw/pci-host/gpex.h b/include/hw/pci-host/gpex.h
> index 68c9348..db26b3e 100644
> --- a/include/hw/pci-host/gpex.h
> +++ b/include/hw/pci-host/gpex.h
> @@ -51,6 +51,9 @@ typedef struct GPEXHost {
> MemoryRegion io_ioport;
> MemoryRegion io_mmio;
> qemu_irq irq[GPEX_NUM_IRQS];
> + uint32_t irq_num[GPEX_NUM_IRQS];
This is an int when calling gpex_set_irq_num() and then used as an int
later, requiring a cast. Why not just make it an int here and in the API?
> } GPEXHost;
>
> +int gpex_set_irq_num(GPEXHost *s, int index, uint32_t gsi);
> +
> #endif /* HW_GPEX_H */
> --
> 2.5.5
>
>
next prev parent reply other threads:[~2017-09-11 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 21:02 [Qemu-devel] [PATCH RESEND v3 0/3] Generic PCIe host bridge INTx determination for INTx routing Eric Auger
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 1/3] hw/pci-host/gpex: Set INTx index/gsi mapping Eric Auger
2017-09-11 12:41 ` Andrew Jones [this message]
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 2/3] hw/arm/virt: Set INTx/gsi mapping Eric Auger
2017-09-11 12:42 ` Andrew Jones
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 3/3] hw/pci-host/gpex: Implement PCI INTx routing Eric Auger
2017-09-11 12:52 ` Andrew Jones
2017-09-01 7:37 ` [Qemu-devel] [PATCH RESEND v3 0/3] Generic PCIe host bridge INTx determination for " Auger Eric
2017-09-01 14:45 ` Feng Kan
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=20170911124154.lpckigdp32kfiisd@hawk.localdomain \
--to=drjones@redhat.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pranavkumar@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.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 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).