From: Rashmica Gupta <rashmica.g@gmail.com>
To: qemu-arm@nongnu.org
Cc: andrew@aj.id.au, peter.maydell@linaro.org, clg@kaod.org,
qemu-devel@nongnu.org, joel@jms.id.au
Subject: Re: [Qemu-devel] [PATCH 0/2] Add Aspeed GPIO controller model
Date: Mon, 15 Jul 2019 16:20:51 +1000 [thread overview]
Message-ID: <a5a7ebddcb737793aa7d6ba84db93b44e00cf7ac.camel@gmail.com> (raw)
In-Reply-To: <20190715061925.28030-1-rashmica.g@gmail.com>
Doh! Forgot the v2 tag!
On Mon, 2019-07-15 at 16:19 +1000, Rashmica Gupta wrote:
> Rebased on Peter's target-arm.next branch.
>
> v2: Addressed Andrew's feedback, added debounce regs, renamed get/set
> to
> read/write to minimise confusion with a 'set' of registers.
>
> Rashmica Gupta (2):
> hw/gpio: Add basic Aspeed GPIO model for AST2400 and AST2500
> aspeed: add a GPIO controller to the SoC
>
> hw/arm/aspeed_soc.c | 17 +
> hw/gpio/Makefile.objs | 1 +
> hw/gpio/aspeed_gpio.c | 891
> ++++++++++++++++++++++++++++++++++
> include/hw/arm/aspeed_soc.h | 3 +
> include/hw/gpio/aspeed_gpio.h | 92 ++++
> 5 files changed, 1004 insertions(+)
> create mode 100644 hw/gpio/aspeed_gpio.c
> create mode 100644 include/hw/gpio/aspeed_gpio.h
>
next prev parent reply other threads:[~2019-07-15 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 6:19 [Qemu-devel] [PATCH 0/2] Add Aspeed GPIO controller model Rashmica Gupta
2019-07-15 6:19 ` [Qemu-devel] [PATCH 1/2] hw/gpio: Add basic Aspeed GPIO model for AST2400 and AST2500 Rashmica Gupta
2019-07-15 6:19 ` [Qemu-devel] [PATCH 2/2] aspeed: add a GPIO controller to the SoC Rashmica Gupta
2019-07-15 6:20 ` Rashmica Gupta [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-18 8:51 [Qemu-devel] [PATCH 0/2] Add Aspeed GPIO controller model Rashmica Gupta
2019-06-18 9:24 ` Cédric Le Goater
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=a5a7ebddcb737793aa7d6ba84db93b44e00cf7ac.camel@gmail.com \
--to=rashmica.g@gmail.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--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).