From: Thomas Huth <thuth@redhat.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Yang Zhong" <yang.zhong@intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-arm@nongnu.org,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PATCH v3 2/8] hw/intc: Only build the xlnx-iomod-intc device for the MicroBlaze PMU
Date: Sat, 17 Aug 2019 12:19:25 +0200 [thread overview]
Message-ID: <20190817101931.28386-3-thuth@redhat.com> (raw)
In-Reply-To: <20190817101931.28386-1-thuth@redhat.com>
From: Philippe Mathieu-Daudé <philmd@redhat.com>
The Xilinx I/O Module Interrupt Controller is only used by the
MicroBlaze PMU, not by the AArch64 machine.
Move it from the generic ZynqMP object list to the PMU specific.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20190427141459.19728-3-philmd@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
hw/intc/Makefile.objs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/intc/Makefile.objs b/hw/intc/Makefile.objs
index 03019b9a03..f726d87532 100644
--- a/hw/intc/Makefile.objs
+++ b/hw/intc/Makefile.objs
@@ -3,7 +3,7 @@ common-obj-$(CONFIG_I8259) += i8259_common.o i8259.o
common-obj-$(CONFIG_PL190) += pl190.o
common-obj-$(CONFIG_PUV3) += puv3_intc.o
common-obj-$(CONFIG_XILINX) += xilinx_intc.o
-common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-pmu-iomod-intc.o
+common-obj-$(CONFIG_XLNX_ZYNQMP_PMU) += xlnx-pmu-iomod-intc.o
common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-zynqmp-ipi.o
common-obj-$(CONFIG_ETRAXFS) += etraxfs_pic.o
common-obj-$(CONFIG_IMX) += imx_avic.o imx_gpcv2.o
--
2.18.1
next prev parent reply other threads:[~2019-08-17 10:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 10:19 [Qemu-devel] [PATCH v3 0/8] Kconfig switches Thomas Huth
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 1/8] hw/Kconfig: Move the generic XLNX_ZYNQMP to the root hw/Kconfig Thomas Huth
2019-08-17 10:19 ` Thomas Huth [this message]
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 3/8] hw/dma: Do not build the xlnx_dpdma device for the MicroBlaze machines Thomas Huth
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 4/8] hw/core: Add a config switch for the "register" device Thomas Huth
2019-08-19 11:54 ` Philippe Mathieu-Daudé
2019-08-19 20:07 ` Alistair Francis
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 5/8] hw/core: Add a config switch for the "or-irq" device Thomas Huth
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 6/8] hw/core: Add a config switch for the "split-irq" device Thomas Huth
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 7/8] hw/misc: Add a config switch for the "unimplemented" device Thomas Huth
2019-08-19 12:47 ` Philippe Mathieu-Daudé
2019-08-17 10:19 ` [Qemu-devel] [PATCH v3 8/8] hw/core: Add a config switch for the generic loader device Thomas Huth
2019-08-19 17:47 ` [Qemu-devel] [PATCH v3 0/8] Kconfig switches Paolo Bonzini
2019-08-19 19:29 ` Thomas Huth
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=20190817101931.28386-3-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yang.zhong@intel.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).