From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Esteban Bosse" <estebanbosse@gmail.com>,
qemu-arm@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Joel Stanley" <joel@jms.id.au>
Subject: [RFC PATCH v2 0/5] hw/misc: Add LED device
Date: Fri, 12 Jun 2020 19:54:35 +0200 [thread overview]
Message-ID: <20200612175440.9901-1-f4bug@amsat.org> (raw)
Hello,
These patches are part of the GSoC unselected 'QEMU visualizer'
project. As the AVR port is not merged, I switched to microbit
to keep working on it.
This series presents a proof of concept of LED device that can
be easily connected to a GPIO.
The LED emit QMP events, so an external visualizer can display
the LED events.
Since v1: addressed Eric Blake review comments
- Added QMP rate limit
This is stable enough to be used for the GSoC UI.
Next steps planned:
- integrate Zephyr test
- have a centralized container for all the machine's LEDs, to
track state changes in a single place and send less QMP events
(grouping changes, restricted to what actually changed).
[see to include keyboard LEDs].
- look at LED array/matrix such 7segments.
Regards,
Phil.
$ git backport-diff -u rfc-v1
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/5:[0004] [FC] 'hw/misc: Add a LED device'
002/5:[0027] [FC] 'hw/misc/led: Add LED_STATUS_CHANGED QAPI event'
003/5:[----] [--] 'hw/misc/led: Add create_led_by_gpio_id() helper'
004/5:[----] [--] 'hw/arm/microbit: Add a fake LED to use as proof-of-concept with Zephyr'
005/5:[----] [--] 'hw/arm/tosa: Use LED device for the Bluetooth led'
Philippe Mathieu-Daudé (5):
hw/misc: Add a LED device
hw/misc/led: Add LED_STATUS_CHANGED QAPI event
hw/misc/led: Add create_led_by_gpio_id() helper
hw/arm/microbit: Add a fake LED to use as proof-of-concept with Zephyr
hw/arm/tosa: Use LED device for the Bluetooth led
qapi/led.json | 47 ++++++++++++++++
qapi/qapi-schema.json | 1 +
include/hw/misc/led.h | 45 +++++++++++++++
hw/arm/microbit.c | 3 +
hw/arm/tosa.c | 7 +--
hw/misc/led.c | 126 ++++++++++++++++++++++++++++++++++++++++++
MAINTAINERS | 7 +++
hw/arm/Kconfig | 2 +
hw/misc/Kconfig | 3 +
hw/misc/Makefile.objs | 1 +
hw/misc/trace-events | 3 +
qapi/Makefile.objs | 2 +-
12 files changed, 242 insertions(+), 5 deletions(-)
create mode 100644 qapi/led.json
create mode 100644 include/hw/misc/led.h
create mode 100644 hw/misc/led.c
--
2.21.3
next reply other threads:[~2020-06-12 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:54 Philippe Mathieu-Daudé [this message]
2020-06-12 17:54 ` [RFC PATCH v2 1/5] hw/misc: Add a LED device Philippe Mathieu-Daudé
2020-06-12 18:44 ` Stefan Weil
2020-06-15 10:55 ` Dr. David Alan Gilbert
2020-06-15 11:19 ` Philippe Mathieu-Daudé
2020-06-15 11:50 ` Dr. David Alan Gilbert
2020-06-12 17:54 ` [RFC PATCH v2 2/5] hw/misc/led: Add LED_STATUS_CHANGED QAPI event Philippe Mathieu-Daudé
2020-06-15 16:05 ` Peter Maydell
2020-06-12 17:54 ` [RFC PATCH v2 3/5] hw/misc/led: Add create_led_by_gpio_id() helper Philippe Mathieu-Daudé
2020-06-12 17:54 ` [RFC PATCH v2 4/5] hw/arm/microbit: Add a fake LED to use as proof-of-concept with Zephyr Philippe Mathieu-Daudé
2020-06-15 16:02 ` Peter Maydell
2020-06-15 16:10 ` Philippe Mathieu-Daudé
2020-06-12 17:54 ` [RFC PATCH v2 5/5] hw/arm/tosa: Use LED device for the Bluetooth led Philippe Mathieu-Daudé
2020-06-15 16:00 ` Peter Maydell
2020-06-15 16:18 ` Philippe Mathieu-Daudé
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=20200612175440.9901-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=estebanbosse@gmail.com \
--cc=joel@jms.id.au \
--cc=kraxel@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).