qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vikram Garhwal <fnu.vikram@xilinx.com>
To: qemu-devel@nongnu.org
Cc: francisco.iglesias@xilinx.com, jasowang@redhat.com,
	Vikram Garhwal <fnu.vikram@xilinx.com>
Subject: [[PATCH v2 0/4] Introduce Xlnx ZynqMP CAN controller for QEMU
Date: Fri, 17 Apr 2020 11:29:25 -0700	[thread overview]
Message-ID: <1587148169-173268-1-git-send-email-fnu.vikram@xilinx.com> (raw)

 Example for single CAN:
      -object can-bus,id=canbus0 \
      -global driver=xlnx.zynqmp-can,property=canbus0,value=canbus0 \
      -object can-host-socketcan,id=socketcan0,if=vcan0,canbus=canbus0

 Example for connecting both CAN:
      -object can-bus,id=canbus0 -object can-bus,id=canbus1 \
      -global driver=xlnx.zynqmp-can,property=canbus0,value=canbus0 \
      -global driver=xlnx.zynqmp-can,property=canbus1,value=canbus1 \
      -object can-host-socketcan,id=socketcan0,if=vcan0,canbus=canbus0 \
      -object can-host-soc

Changelog:

v1 -> v2:
    Rename the CAN device state and address code style issues.
    Connect the CAN device to Xlnx-ZCU102 board.
    Add maintainer entry.
    Add QTEST for the CAN device.

Vikram Garhwal (4):
  MAINTAINERS: Add maintainer entry for Xilinx CAN
  hw/net/can: Introduce Xlnx ZynqMP CAN controller for QEMU
  hw/net/can: Connect Xlnx ZynqMP CAN controller to ZCU102 machine
  hw/net/can: Introduce QTEST for Xlnx CAN controller

 MAINTAINERS                      |    7 +
 hw/arm/xlnx-zynqmp.c             |   26 +
 hw/net/can/Makefile.objs         |    1 +
 hw/net/can/xlnx-zynqmp-can.c     | 1113 ++++++++++++++++++++++++++++++++++++++
 include/hw/arm/xlnx-zynqmp.h     |    3 +
 include/hw/net/xlnx-zynqmp-can.h |   76 +++
 tests/qtest/Makefile.include     |    1 +
 tests/qtest/xlnx-can-test.c      |  367 +++++++++++++
 8 files changed, 1594 insertions(+)
 create mode 100644 hw/net/can/xlnx-zynqmp-can.c
 create mode 100644 include/hw/net/xlnx-zynqmp-can.h
 create mode 100644 tests/qtest/xlnx-can-test.c

--
2.7.4



             reply	other threads:[~2020-04-17 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 18:29 Vikram Garhwal [this message]
2020-04-17 18:29 ` [[PATCH v2 1/4] MAINTAINERS: Add maintainer entry for Xilinx CAN Vikram Garhwal
2020-04-17 18:29 ` [[PATCH v2 2/4] hw/net/can: Introduce Xlnx ZynqMP CAN controller for QEMU Vikram Garhwal
2020-04-17 18:29 ` [[PATCH v2 3/4] hw/net/can: Connect Xlnx ZynqMP CAN controller to ZCU102 machine Vikram Garhwal
2020-04-17 18:29 ` [[PATCH v2 4/4] hw/net/can: Introduce QTEST for Xlnx CAN controller Vikram Garhwal
2020-04-17 19:55 ` [[PATCH v2 0/4] Introduce Xlnx ZynqMP CAN controller for QEMU no-reply

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=1587148169-173268-1-git-send-email-fnu.vikram@xilinx.com \
    --to=fnu.vikram@xilinx.com \
    --cc=francisco.iglesias@xilinx.com \
    --cc=jasowang@redhat.com \
    --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).