qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Julia Suvorova <jusual@mail.ru>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Jim Mussared" <jim@groklearning.com>,
	"Steffen Görtz" <mail@steffen-goertz.de>,
	"Thomas Huth" <thuth@redhat.com>, "Joel Stanley" <joel@jms.id.au>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] arm: Add nRF51 SoC UART support
Date: Thu, 25 Oct 2018 09:36:25 +0100	[thread overview]
Message-ID: <20181025083625.GA25480@stefanha-x1.localdomain> (raw)
In-Reply-To: <20181025005052.27661-1-jusual@mail.ru>

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

On Thu, Oct 25, 2018 at 03:50:49AM +0300, Julia Suvorova via Qemu-devel wrote:
> This series adds support for the nRF51 SoC UART, that used in
> BBC Micro:bit board, and QTest for it.
> 
> v3:
>     * serial_hd() moved to the board code
>     * sysbus_init_child_obj() used for initialization
>     * qemu_chr_fe_accept_input() called after byte popping
> 
> v2:
>     * Suspend/Enable functionality added
>     * Connection to SoC moved to a separate patch
>     * Added QTest for checking reception functionality
>     * Mini-kernel test changed to fit current implementation
>     * Addressed review comments on R_*, uart_can_receive, VMState,
>       uart_transmit
> 
> Julia Suvorova (3):
>   hw/char: Implement nRF51 SoC UART
>   hw/arm/nrf51_soc: Connect UART to nRF51 SoC
>   tests/boot-serial-test: Add microbit board testcase
> 
>  hw/arm/microbit.c            |   2 +
>  hw/arm/nrf51_soc.c           |  20 +++
>  hw/char/Makefile.objs        |   1 +
>  hw/char/nrf51_uart.c         | 330 +++++++++++++++++++++++++++++++++++
>  hw/char/trace-events         |   4 +
>  include/hw/arm/nrf51_soc.h   |   3 +
>  include/hw/char/nrf51_uart.h |  78 +++++++++
>  tests/boot-serial-test.c     |  19 ++
>  8 files changed, 457 insertions(+)
>  create mode 100644 hw/char/nrf51_uart.c
>  create mode 100644 include/hw/char/nrf51_uart.h
> 
> -- 
> 2.17.1
> 
> 

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2018-10-25  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  0:50 [Qemu-devel] [PATCH v3 0/3] arm: Add nRF51 SoC UART support Julia Suvorova
2018-10-25  0:50 ` [Qemu-devel] [PATCH v3 1/3] hw/char: Implement nRF51 SoC UART Julia Suvorova
2018-10-25  0:50 ` [Qemu-devel] [PATCH v3 2/3] hw/arm/nrf51_soc: Connect UART to nRF51 SoC Julia Suvorova
2018-10-25  9:25   ` Alistair Francis
2018-10-25  0:50 ` [Qemu-devel] [PATCH v3 3/3] tests/boot-serial-test: Add microbit board testcase Julia Suvorova
2018-10-25  8:36 ` Stefan Hajnoczi [this message]
2018-10-29 14:37 ` [Qemu-devel] [PATCH v3 0/3] arm: Add nRF51 SoC UART support Peter Maydell
2018-11-01 10:19   ` Stefan Hajnoczi

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=20181025083625.GA25480@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=jim@groklearning.com \
    --cc=joel@jms.id.au \
    --cc=jusual@mail.ru \
    --cc=mail@steffen-goertz.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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).