From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Alistair Francis" <alistair@alistair23.me>,
qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>
Subject: [PATCH 0/3] hw/arm/raspi: Split the UART block from the AUX block
Date: Mon, 7 Oct 2019 19:06:43 +0200 [thread overview]
Message-ID: <20191007170646.14961-1-f4bug@amsat.org> (raw)
The BCM2838 has many more peripherals than his little brother,
the BCM2837. With the raspi4, the Linux kernel takes more steps
to configure the various MUXed devices. At some point it started
to bug me, so I plan to add a dummy simple BCM2835_SPI block.
It is cleaner to add it as a separate device than mixed with the
AUX block. As a first step, split the UART block out.
Since this part is self-contained and my raspi4 branch is getting
too big, I'm sending it as a single series.
Regards,
Phil.
Philippe Mathieu-Daudé (3):
hw/char: Add the BCM2835 miniuart
hw/char/bcm2835_aux: Use the BCM2835 miniuart block
hw: Move BCM2835 AUX device from hw/char/ to hw/misc/
hw/char/Makefile.objs | 2 +-
hw/char/bcm2835_aux.c | 317 -----------------------
hw/char/bcm2835_miniuart.c | 327 ++++++++++++++++++++++++
hw/char/trace-events | 4 +
hw/misc/Makefile.objs | 1 +
hw/misc/bcm2835_aux.c | 189 ++++++++++++++
hw/misc/trace-events | 4 +
include/hw/arm/bcm2835_peripherals.h | 2 +-
include/hw/char/bcm2835_miniuart.h | 37 +++
include/hw/{char => misc}/bcm2835_aux.h | 10 +-
10 files changed, 567 insertions(+), 326 deletions(-)
delete mode 100644 hw/char/bcm2835_aux.c
create mode 100644 hw/char/bcm2835_miniuart.c
create mode 100644 hw/misc/bcm2835_aux.c
create mode 100644 include/hw/char/bcm2835_miniuart.h
rename include/hw/{char => misc}/bcm2835_aux.h (73%)
--
2.21.0
next reply other threads:[~2019-10-07 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 17:06 Philippe Mathieu-Daudé [this message]
2019-10-07 17:06 ` [PATCH 1/3] hw/char: Add the BCM2835 miniuart Philippe Mathieu-Daudé
2019-10-11 22:05 ` Alistair Francis
2019-10-07 17:06 ` [PATCH 2/3] hw/char/bcm2835_aux: Use the BCM2835 miniuart block Philippe Mathieu-Daudé
2019-10-07 17:06 ` [PATCH 3/3] hw: Move BCM2835 AUX device from hw/char/ to hw/misc/ Philippe Mathieu-Daudé
2019-10-07 21:09 ` [PATCH 0/3] hw/arm/raspi: Split the UART block from the AUX block no-reply
2019-10-17 16:23 ` Peter Maydell
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=20191007170646.14961-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=Andrew.Baumann@microsoft.com \
--cc=alistair@alistair23.me \
--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).