From: Subbaraya Sundeep <sundeep.lkml@gmail.com>
To: qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, crosthwaite.peter@gmail.com,
Subbaraya Sundeep <sundeep.lkml@gmail.com>
Subject: [Qemu-devel] [Qemu-devel RFC v2 0/4] Add support for Smartfusion2 SoC
Date: Sun, 9 Apr 2017 16:49:14 +0530 [thread overview]
Message-ID: <1491736758-19540-1-git-send-email-sundeep.lkml@gmail.com> (raw)
Hi Qemu-devel,
I am trying to add Smartfusion2 SoC.
SoC is from Microsemi and System on Module(SOM)
board is from Emcraft systems. Smartfusion2 has hardened
Microcontroller(Cortex-M3)based Sub System and FPGA fabric.
At the moment only system timer, sysreg and SPI
controller are modelled.
Testing:
./arm-softmmu/qemu-system-arm -M smartfusion2-som -serial mon:stdio \
-kernel u-boot.bin -display none -drive file=spi.bin,if=mtd,format=raw
U-boot is from Emcraft with modified SPI driver not to use PDMA.
Linux is 4.5 linux with Smartfusion2 SoC dts and clocksource
driver added by myself @
https://github.com/Subbaraya-Sundeep/linux.git
Baremetal elfs from Microsemi Softconsole IDE are also working.
Changes from v1:
Added SPI controller.
Thanks,
Sundeep
Subbaraya Sundeep (4):
msf2: Add Smartfusion2 System timer
msf2: Microsemi Smartfusion2 System Register block.
msf2: Add Smartfusion2 SPI controller
msf2: Add Emcraft's Smartfusion2 SOM kit.
default-configs/arm-softmmu.mak | 1 +
hw/arm/Makefile.objs | 2 +-
hw/arm/msf2_soc.c | 141 +++++++++++++
hw/misc/Makefile.objs | 1 +
hw/misc/msf2_sysreg.c | 168 +++++++++++++++
hw/ssi/Makefile.objs | 1 +
hw/ssi/msf2_spi.c | 449 ++++++++++++++++++++++++++++++++++++++++
hw/timer/Makefile.objs | 1 +
hw/timer/msf2_timer.c | 273 ++++++++++++++++++++++++
9 files changed, 1036 insertions(+), 1 deletion(-)
create mode 100644 hw/arm/msf2_soc.c
create mode 100644 hw/misc/msf2_sysreg.c
create mode 100644 hw/ssi/msf2_spi.c
create mode 100644 hw/timer/msf2_timer.c
--
2.5.0
next reply other threads:[~2017-04-09 11:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 11:19 Subbaraya Sundeep [this message]
2017-04-09 11:19 ` [Qemu-devel] [Qemu-devel RFC v2 1/4] msf2: Add Smartfusion2 System timer Subbaraya Sundeep
2017-04-14 21:28 ` Alistair Francis
2017-04-17 10:21 ` sundeep subbaraya
2017-04-24 17:44 ` Alistair Francis
2017-04-24 17:58 ` Peter Maydell
2017-04-25 10:07 ` sundeep subbaraya
2017-04-25 10:36 ` sundeep subbaraya
2017-04-27 18:53 ` Alistair Francis
2017-04-28 14:19 ` sundeep subbaraya
2017-04-09 11:19 ` [Qemu-devel] [Qemu-devel RFC v2 2/4] msf2: Microsemi Smartfusion2 System Register block Subbaraya Sundeep
2017-04-14 21:32 ` Alistair Francis
2017-04-17 10:25 ` sundeep subbaraya
2017-04-09 11:19 ` [Qemu-devel] [Qemu-devel RFC v2 3/4] msf2: Add Smartfusion2 SPI controller Subbaraya Sundeep
2017-04-09 11:19 ` [Qemu-devel] [Qemu-devel RFC v2 4/4] msf2: Add Emcraft's Smartfusion2 SOM kit Subbaraya Sundeep
2017-04-14 21:12 ` Alistair Francis
2017-04-17 10:44 ` sundeep subbaraya
2017-04-24 17:53 ` Alistair Francis
2017-04-25 10:04 ` sundeep subbaraya
2017-04-13 3:21 ` [Qemu-devel] [Qemu-devel RFC v2 0/4] Add support for Smartfusion2 SoC sundeep subbaraya
2017-04-13 9:44 ` Peter Maydell
2017-04-13 10:33 ` sundeep subbaraya
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=1491736758-19540-1-git-send-email-sundeep.lkml@gmail.com \
--to=sundeep.lkml@gmail.com \
--cc=crosthwaite.peter@gmail.com \
--cc=peter.maydell@linaro.org \
--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).