qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alistair Francis" <alistair.francis@xilinx.com>,
	"Edgar E . Iglesias" <edgar.iglesias@xilinx.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Jason Wang" <jasowang@redhat.com>
Subject: [Qemu-devel] [RFC PATCH v2 3/9] hw/net/cadence_gem: add FDT aliases
Date: Mon,  8 Jan 2018 23:00:48 -0300	[thread overview]
Message-ID: <20180109020054.32553-4-f4bug@amsat.org> (raw)
In-Reply-To: <20180109020054.32553-1-f4bug@amsat.org>

Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
 hw/net/cadence_gem.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/hw/net/cadence_gem.c b/hw/net/cadence_gem.c
index 3943187572..34ff738bf7 100644
--- a/hw/net/cadence_gem.c
+++ b/hw/net/cadence_gem.c
@@ -25,6 +25,7 @@
 #include "qemu/osdep.h"
 #include <zlib.h> /* For crc32 */
 
+#include "hw/sysbus-fdt.h"
 #include "hw/net/cadence_gem.h"
 #include "qapi/error.h"
 #include "qemu/log.h"
@@ -1552,6 +1553,15 @@ static const TypeInfo gem_info = {
 
 static void gem_register_types(void)
 {
+    static const char *gem_fdt_aliases[] = {
+        "cdns,gem",
+        "cdns,zynq-gem",    /* Zynq-7xxx SoC */
+        "xlnx.ps7-ethernet",
+        "cdns,zynqmp-gem",  /* Zynq Ultrascale+ MPSoC */
+        NULL
+    };
+
+    type_register_fdt_aliases(TYPE_CADENCE_GEM, gem_fdt_aliases);
     type_register_static(&gem_info);
 }
 
-- 
2.15.1

  parent reply	other threads:[~2018-01-09  2:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  2:00 [Qemu-devel] [RFC PATCH v2 0/9] resolv device by Flattened Device Tree alias name Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 1/9] hw/sysbus: add helpers to register FDT aliases Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 2/9] hw/char/cadence_uart: add " Philippe Mathieu-Daudé
2018-01-09  2:00 ` Philippe Mathieu-Daudé [this message]
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 4/9] hw/timer/cadence_ttc: " Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 5/9] hw/dma/axidma: add 'xlnx, eth-dma' FDT alias Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 6/9] hw/usb/hcd-ehci: add 'xlnx, ps7-usb' FDT aliases Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 7/9] hw/ssi/xlnx-spips: add 'xlnx.zynq-qspi' FDT alias Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 8/9] hw/dma/xlnx_dpdma: add 'xlnx, axi-dpdma-1.0' " Philippe Mathieu-Daudé
2018-01-09  2:00 ` [Qemu-devel] [RFC PATCH v2 9/9] hw/arm/xlnx-zynqmp: use Linux FDT names Philippe Mathieu-Daudé
2018-01-09  9:51   ` 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=20180109020054.32553-4-f4bug@amsat.org \
    --to=f4bug@amsat.org \
    --cc=afaerber@suse.de \
    --cc=alistair.francis@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-arm@nongnu.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).