qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com, edgar.iglesias@gmail.com
Cc: peter.crosthwaite@petalogix.com, john.williams@petalogix.com
Subject: [Qemu-devel] [RFC PATCH v1 0/4] SPI bus support + Xilinx SPI controller
Date: Fri, 30 Mar 2012 16:37:09 +1000	[thread overview]
Message-ID: <cover.1333088411.git.peter.crosthwaite@petalogix.com> (raw)

Add support for Serial Peripheral interface (SPI) as a proper bus standard. Includes an example device (m25p80 SPI flash), an example controller (Xilinx XPS SPI) and adds it to all to a machine model (petalogix_ml605_mmu.c).

Patch 1 adds the Serial Peripheral Interface (SPI) protocol as a bus and defines a QOM type for slave devices. The approach to doing this is based looseley on the existing I2C QOMification.

Patch 2 is a device model for the m25p80 style SPI flash chip.

Patch 3 is  the Xilinx XPS SPI contoller. Its a sysbus device that instantiates a spi bus, and interfaces the two (as per the controllers functionality)

Patch 4 instantiates the XPS SPI controller in the petalogix ML605 reference platform and connects one m25p80 to it.

Peter A. G. Crosthwaite (4):
  SPI: initial support
  m25p80: initial verion
  xilinx_spi: initial version
  petalogix-ml605: added spi controller with m25p80

 Makefile.target          |    3 +
 hw/m25p80.c              |  495 ++++++++++++++++++++++++++++++++++++++++++++++
 hw/petalogix_ml605_mmu.c |   19 ++
 hw/spi.c                 |  175 ++++++++++++++++
 hw/spi.h                 |   86 ++++++++
 hw/xilinx_spi.c          |  477 ++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 1255 insertions(+), 0 deletions(-)
 create mode 100644 hw/m25p80.c
 create mode 100644 hw/spi.c
 create mode 100644 hw/spi.h
 create mode 100644 hw/xilinx_spi.c

-- 
1.7.3.2

             reply	other threads:[~2012-03-30  6:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  6:37 Peter A. G. Crosthwaite [this message]
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 1/4] SPI: initial support Peter A. G. Crosthwaite
2012-03-30  7:37   ` Peter Maydell
2012-03-30  7:50     ` Peter Crosthwaite
2012-04-02 17:39   ` Peter Maydell
2012-04-02 23:51     ` Peter Crosthwaite
2012-04-03  0:48       ` Peter Crosthwaite
2012-04-03 17:45       ` Paul Brook
2012-04-03 18:08         ` Peter Maydell
2012-04-03 21:22           ` Paul Brook
2012-04-04  0:48             ` Peter Crosthwaite
2012-04-04 16:52               ` Paul Brook
2012-04-05  0:32                 ` Peter Crosthwaite
2012-04-05  7:18                   ` Peter Maydell
2012-04-02 23:57     ` Peter Crosthwaite
2012-04-03  0:27       ` Andreas Färber
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 2/4] m25p80: initial verion Peter A. G. Crosthwaite
2012-04-03  7:03   ` Stefan Hajnoczi
2012-04-04 12:53   ` Andreas Färber
2012-06-05  0:47     ` Peter Crosthwaite
2012-06-05 12:38       ` Andreas Färber
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 3/4] xilinx_spi: initial version Peter A. G. Crosthwaite
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 4/4] petalogix-ml605: added spi controller with m25p80 Peter A. G. Crosthwaite

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=cover.1333088411.git.peter.crosthwaite@petalogix.com \
    --to=peter.crosthwaite@petalogix.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@petalogix.com \
    --cc=paul@codesourcery.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).