From: Sergio Lopez <slp@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Sergio Lopez" <slp@redhat.com>
Subject: [PATCH v2 0/6] Implement virtio-multitouch and enable GTK3 to use it
Date: Thu, 16 Mar 2023 13:06:18 +0100 [thread overview]
Message-ID: <20230316120624.46410-1-slp@redhat.com> (raw)
This series adds a virtio-multitouch device to the family of devices emulated
by virtio-input implementing the Multi-touch protocol as descripted here:
https://www.kernel.org/doc/html/latest/input/multi-touch-protocol.html?highlight=multi+touch
It also extends the GTK UI backend to be able to receive multi-touch events
and transpose them to a guest, so the latter can recognize them as gestures
when appropriate.
An example of this in action can be seen here:
https://fosstodon.org/@slp/109545849296546767
Since v1:
- Split 0002 patch to implement ui, virtio-input-hid and virtio-input-pci
changes in different patches (Marc-André).
- Fix versioning in qapi/ui.json (Marc-André).
- Print a warning if touch->sequence >= INPUT_EVENT_SLOTS_MAX (Marc-André).
- Only send SYN_REPORT once, if needed (Marc-André).
- Rebase and collect R-b.
Sergio Lopez (6):
virtio-input: generalize virtio_input_key_config()
ui: add the infrastructure to support MT events
virtio-input: add a virtio-mulitouch device
virtio-input-pci: add virtio-multitouch-pci
ui: add helpers for virtio-multitouch events
ui/gtk: enable backend to send multi-touch events
hw/input/virtio-input-hid.c | 156 +++++++++++++++++++++++++++----
hw/virtio/virtio-input-pci.c | 25 ++++-
include/hw/virtio/virtio-input.h | 9 +-
include/ui/input.h | 8 ++
qapi/ui.json | 45 ++++++++-
replay/replay-input.c | 18 ++++
ui/gtk.c | 92 ++++++++++++++++++
ui/input.c | 42 +++++++++
ui/trace-events | 1 +
9 files changed, 365 insertions(+), 31 deletions(-)
--
2.38.1
next reply other threads:[~2023-03-16 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 12:06 Sergio Lopez [this message]
2023-03-16 12:06 ` [PATCH v2 1/6] virtio-input: generalize virtio_input_key_config() Sergio Lopez
2023-03-16 12:06 ` [PATCH v2 2/6] ui: add the infrastructure to support MT events Sergio Lopez
2023-03-17 8:03 ` Marc-André Lureau
2023-03-16 12:06 ` [PATCH v2 3/6] virtio-input: add a virtio-mulitouch device Sergio Lopez
2023-03-17 8:03 ` Marc-André Lureau
2023-03-16 12:06 ` [PATCH v2 4/6] virtio-input-pci: add virtio-multitouch-pci Sergio Lopez
2023-03-17 8:05 ` Marc-André Lureau
2023-03-16 12:06 ` [PATCH v2 5/6] ui: add helpers for virtio-multitouch events Sergio Lopez
2023-03-16 12:06 ` [PATCH v2 6/6] ui/gtk: enable backend to send multi-touch events Sergio Lopez
2023-03-17 8:02 ` Marc-André Lureau
2023-03-20 10:16 ` Sergio Lopez
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=20230316120624.46410-1-slp@redhat.com \
--to=slp@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--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).