From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH 0/6] arm/stellaris: convert gamepad input device to qdev
Date: Tue, 17 Oct 2023 13:22:56 +0100 [thread overview]
Message-ID: <20231017122302.1692902-1-peter.maydell@linaro.org> (raw)
(I had this all ready to go before I went off on holiday two
weeks ago, except I forgot to actually *send* the emails...)
This patchseries converts the stellaris board's gamepad input device
to qdev. This isn't a very important bit of conversion (I was just
looking for a small tail-end-of-the-week task), but it does reduce by
one the number of users of a couple of legacy APIs: vmstate_register()
and qemu_add_kbd_event_handler().
I've included Kevin's qdev_prop_set_array() patch here, because I
wanted an array property and it doesn't seem sensible to write it the
old way and have another thing that needs converting. I'm assuming
that by the time this patchset gets reviewed and committed that
one will already be upstream.
thanks
-- PMM
Kevin Wolf (1):
qdev: Add qdev_prop_set_array()
Peter Maydell (5):
hw/input/stellaris_input: Rename to stellaris_gamepad
hw/input/stellaris_gamepad: Rename structs to our usual convention
hw/input/stellaris_gamepad: Remove StellarisGamepadButton struct
hw/input/stellaris_input: Convert to qdev
hw/input/stellaris_gamepad: Convert to qemu_input_handler_register()
include/hw/input/gamepad.h | 18 -----
include/hw/input/stellaris_gamepad.h | 39 ++++++++++
include/hw/qdev-properties.h | 3 +
hw/arm/stellaris.c | 34 ++++++---
hw/core/qdev-properties.c | 21 ++++++
hw/input/stellaris_gamepad.c | 102 +++++++++++++++++++++++++++
hw/input/stellaris_input.c | 93 ------------------------
hw/arm/Kconfig | 2 +-
hw/input/Kconfig | 2 +-
hw/input/meson.build | 2 +-
10 files changed, 193 insertions(+), 123 deletions(-)
delete mode 100644 include/hw/input/gamepad.h
create mode 100644 include/hw/input/stellaris_gamepad.h
create mode 100644 hw/input/stellaris_gamepad.c
delete mode 100644 hw/input/stellaris_input.c
--
2.34.1
next reply other threads:[~2023-10-17 12:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 12:22 Peter Maydell [this message]
2023-10-17 12:22 ` [PATCH 1/6] hw/input/stellaris_input: Rename to stellaris_gamepad Peter Maydell
2023-10-17 12:44 ` Philippe Mathieu-Daudé
2023-10-17 12:22 ` [PATCH 2/6] hw/input/stellaris_gamepad: Rename structs to our usual convention Peter Maydell
2023-10-17 12:44 ` Philippe Mathieu-Daudé
2023-10-17 12:22 ` [PATCH 3/6] qdev: Add qdev_prop_set_array() Peter Maydell
2023-10-17 12:23 ` [PATCH 4/6] hw/input/stellaris_gamepad: Remove StellarisGamepadButton struct Peter Maydell
2023-10-17 12:44 ` Philippe Mathieu-Daudé
2023-10-17 12:52 ` Peter Maydell
2023-10-17 13:09 ` Philippe Mathieu-Daudé
2023-10-17 12:23 ` [PATCH 5/6] hw/input/stellaris_input: Convert to qdev Peter Maydell
2023-10-17 12:48 ` Philippe Mathieu-Daudé
2023-10-17 12:49 ` Peter Maydell
2023-10-17 12:23 ` [PATCH 6/6] hw/input/stellaris_gamepad: Convert to qemu_input_handler_register() Peter Maydell
2023-10-17 13:09 ` Philippe Mathieu-Daudé
2023-10-19 21:47 ` Philippe Mathieu-Daudé
2023-10-30 10:39 ` [PATCH 0/6] arm/stellaris: convert gamepad input device to qdev Philippe Mathieu-Daudé
2023-10-30 11:29 ` Peter Maydell
2023-10-30 13:19 ` 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=20231017122302.1692902-1-peter.maydell@linaro.org \
--to=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).