BMC/Intel-BMC/linux.git/drivers/input/misc/xen-kbdfront.c, branch dev-4.18

Input: xen-kbdfront - fix multi-touch XenStore node's locations

2018-10-03T23:59:16+00:00

[ Upstream commit ce6f7d087e2b037f47349c1c36ac97678d02e394 ] kbdif protocol describes multi-touch device parameters as a part of frontend's XenBus configuration nodes while they belong to backend's configuration. Fix this by reading the parameters as defined by the protocol. Fixes: 49aac8204da5 ("Input: xen-kbdfront - add multi-touch support") Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Juergen Gross Signed-off-by: Dmitry Torokhov Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman

Input: xen-kbdfront - do not advertise multi-touch pressure support

2018-01-02T17:41:47+00:00

Some user-space applications expect multi-touch pressure on contact to be reported if it is advertised in device properties. Otherwise, such applications may treat reports not as actual touches, but hovering. Currently this is only advertised, but not reported. Fix this by not advertising that ABS_MT_PRESSURE is supported. Signed-off-by: Oleksandr Andrushchenko Signed-off-by: Andrii Chepurnyi Patchwork-Id: 10140017 Signed-off-by: Dmitry Torokhov

Input: xen-kbdfront - enable auto repeat for xen keyboard frontend driver

2017-08-28T17:31:31+00:00

Long pressed key could not show right in XEN vncviewer after tigervnc client changed the way how to send repeat keys, from "Down Up Down Up ..." to "Down Down ... Up". This will report autorepeat to input by checking if same key being pressed, and let handler process it finally. Signed-off-by: Liang Yan Signed-off-by: Dmitry Torokhov

Input: xen-kbdfront - add multi-touch support

2017-07-09T21:43:26+00:00

Extend xen_kbdfront to provide multi-touch support to unprivileged domains. Signed-off-by: Oleksandr Andrushchenko [dtor: factor out various sub-protocols - multitouch, single touch, keys] Signed-off-by: Dmitry Torokhov

Input: xen-kbdfront - use string constants from PV protocol

2017-06-09T16:56:06+00:00

Xen input para-virtual protocol defines string constants used by both back and frontend. Use those instead of explicit strings in the frontend driver. Signed-off-by: Oleksandr Andrushchenko Signed-off-by: Dmitry Torokhov

Input: xen-kbdfront - add module parameter for setting resolution

2017-04-19T16:02:43+00:00

Add a parameter for setting the resolution of xen-kbdfront in order to be able to cope with a (virtual) frame buffer of arbitrary resolution. While at it remove the pointless second reading of parameters from Xenstore in the device connection phase: all parameters are available during device probing already and that is where they should be read. Signed-off-by: Juergen Gross Signed-off-by: Dmitry Torokhov

Input: convert remaining uses of pr_warning to pr_warn

2017-03-18T00:25:02+00:00

To enable eventual removal of pr_warning This makes pr_warn use consistent for drivers/input Prior to this patch, there were 8 uses of pr_warning and 17 uses of pr_warn in drivers/input Signed-off-by: Joe Perches Signed-off-by: Dmitry Torokhov

xen: make use of xenbus_read_unsigned() in xen-kbdfront

2016-11-07T12:55:20+00:00

Use xenbus_read_unsigned() instead of xenbus_scanf() when possible. This requires to change the type of the reads from int to unsigned, but these cases have been wrong before: negative values are not allowed for the modified cases. Cc: dmitry.torokhov@gmail.com Cc: linux-input@vger.kernel.org Signed-off-by: Juergen Gross Acked-by: David Vrabel

Input: xen-kbdfront - prefer xenbus_write() over xenbus_printf() where possible

2016-07-14T00:27:24+00:00

... as being the simpler variant. Signed-off-by: Jan Beulich Signed-off-by: Dmitry Torokhov

Input: xen - check return value of xenbus_printf

2015-10-23T06:32:01+00:00

Internally, xenbus_printf uses memory allocation, so it can fail under memory pressure, leaving the input device configured as absolute with the backend supplying relative coordinates. Signed-off-by: Insu Yun Reviewed-by: Julien Grall Signed-off-by: Dmitry Torokhov