From: Owen Smith <owen.smith@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Owen Smith <owen.smith@citrix.com>
Subject: [PATCH] kbdif.h: Introduce feature-vkbd-standalone
Date: Thu, 8 Jun 2017 13:09:03 +0000 [thread overview]
Message-ID: <1496927343-29065-1-git-send-email-owen.smith@citrix.com> (raw)
Backends set "feature-vkbd-standalone" to 1 if they can connect
without waiting for the PV framebuffer. If this value is missing
or not 1, then a backend will wait for the PV framebuffer before
connecting, potentially causing the frontend to wait indefinitely.
Frontends set "request-vkbd-standalone" to 1 to request that the
backend does not wait for the PV framebuffer. Frontends that
require a standalone vkbd device should not attempt to connect
unless the backend advertises "feature-vkbd-standalone", and
should set "request-vkbd-standalone".
Backends that are standalone (i.e. do not have an associated PV
framebuffer) do not rescale absolute mouse or touch coordinates
to a the size of the (non-existant) PV framebuffer, and use the
range of [0, 0x7fff] for absolute values.
Signed-off-by: Owen Smith <owen.smith@citrix.com>
---
xen/include/public/io/kbdif.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/xen/include/public/io/kbdif.h b/xen/include/public/io/kbdif.h
index dcbd71a..ca09080 100644
--- a/xen/include/public/io/kbdif.h
+++ b/xen/include/public/io/kbdif.h
@@ -63,6 +63,12 @@
* Backends, which support reporting of multi-touch events
* should set this to 1.
*
+ * feature-vkbd-standalone
+ * Values: <uint>
+ *
+ * Backends, which support a standalone vkbd, without requiring a vfb
+ * device, should set this to 1.
+ *
*------------------------- Pointer Device Parameters ------------------------
*
* width
@@ -98,6 +104,13 @@
*
* Request backend to report multi-touch events.
*
+ * request-vkbd-standalone
+ * Values: <uint>
+ *
+ * Request backend to connect vkbd device without waiting for the
+ * vfb device. Any absolute coordinates will NOT be scaled to
+ * screen size, and will remain in the range [0, 0x7fff]
+ *
*----------------------- Request Transport Parameters -----------------------
*
* event-channel
@@ -165,8 +178,10 @@
#define XENKBD_FIELD_FEAT_ABS_POINTER "feature-abs-pointer"
#define XENKBD_FIELD_FEAT_MTOUCH "feature-multi-touch"
+#define XENKBD_FIELD_FEAT_STANDALONE "feature-vkbd-standalone"
#define XENKBD_FIELD_REQ_ABS_POINTER "request-abs-pointer"
#define XENKBD_FIELD_REQ_MTOUCH "request-multi-touch"
+#define XENKBD_FIELD_REQ_STANDALONE "request-vkbd-standalone"
#define XENKBD_FIELD_RING_GREF "page-gref"
#define XENKBD_FIELD_EVT_CHANNEL "event-channel"
#define XENKBD_FIELD_WIDTH "width"
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-06-08 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 13:09 Owen Smith [this message]
2017-06-12 7:07 ` [PATCH] kbdif.h: Introduce feature-vkbd-standalone Oleksandr Andrushchenko
2017-06-13 14:59 ` Owen Smith
2017-06-14 7:48 ` Oleksandr Andrushchenko
2017-06-14 8:54 ` Paul Durrant
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=1496927343-29065-1-git-send-email-owen.smith@citrix.com \
--to=owen.smith@citrix.com \
--cc=xen-devel@lists.xenproject.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).