fdo-mirrors/libinput
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libinput.git synced 2025-12-20 08:00:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
libinput/test/litest-synaptics.c

139 lines
4.6 KiB
C
Raw Normal View History

Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
/*
* Copyright © 2013 Red Hat, Inc.
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that copyright
* notice and this permission notice appear in supporting documentation, and
* that the name of the copyright holders not be used in advertising or
* publicity pertaining to distribution of the software without specific,
* written prior permission. The copyright holders make no representations
* about the suitability of this software for any purpose. It is provided "as
* is" without express or implied warranty.
*
* THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
* INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
* EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR
* CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
* DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
* TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
* OF THIS SOFTWARE.
*/
#if HAVE_CONFIG_H
#include "config.h"
#endif
#include "litest.h"
#include "litest-int.h"
#include "libinput-util.h"
void litest_synaptics_clickpad_setup(void)
{
struct litest_device *d = litest_create_device(LITEST_SYNAPTICS_CLICKPAD);
litest_set_current_device(d);
}
void
litest_synaptics_clickpad_touch_down(struct litest_device *d,
unsigned int slot,
int x, int y)
{
static int tracking_id;
struct input_event *ev;
struct input_event down[] = {
test: make sure BTN_TOOL_FINGER and BTN_TOUCH are down Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2014-03-21 14:37:27 +10:00
{ .type = EV_KEY, .code = BTN_TOOL_FINGER, .value = 1 },
{ .type = EV_KEY, .code = BTN_TOUCH, .value = 1 },
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
{ .type = EV_ABS, .code = ABS_X, .value = x },
{ .type = EV_ABS, .code = ABS_Y, .value = y },
{ .type = EV_ABS, .code = ABS_PRESSURE, .value = 30 },
{ .type = EV_ABS, .code = ABS_MT_SLOT, .value = slot },
{ .type = EV_ABS, .code = ABS_MT_TRACKING_ID, .value = ++tracking_id },
{ .type = EV_ABS, .code = ABS_MT_POSITION_X, .value = x },
{ .type = EV_ABS, .code = ABS_MT_POSITION_Y, .value = y },
{ .type = EV_SYN, .code = SYN_REPORT, .value = 0 },
};
test: make sure BTN_TOOL_FINGER and BTN_TOUCH are down Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2014-03-21 14:37:27 +10:00
down[2].value = litest_scale(d, ABS_X, x);
down[3].value = litest_scale(d, ABS_Y, y);
down[7].value = litest_scale(d, ABS_X, x);
down[8].value = litest_scale(d, ABS_Y, y);
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
ARRAY_FOR_EACH(down, ev)
litest_event(d, ev->type, ev->code, ev->value);
}
void
litest_synaptics_clickpad_move(struct litest_device *d,
unsigned int slot,
int x, int y)
{
struct input_event *ev;
struct input_event move[] = {
{ .type = EV_ABS, .code = ABS_MT_SLOT, .value = slot },
{ .type = EV_ABS, .code = ABS_X, .value = x },
{ .type = EV_ABS, .code = ABS_Y, .value = y },
{ .type = EV_ABS, .code = ABS_MT_POSITION_X, .value = x },
{ .type = EV_ABS, .code = ABS_MT_POSITION_Y, .value = y },
{ .type = EV_KEY, .code = BTN_TOOL_FINGER, .value = 1 },
{ .type = EV_KEY, .code = BTN_TOUCH, .value = 1 },
{ .type = EV_SYN, .code = SYN_REPORT, .value = 0 },
};
move[1].value = litest_scale(d, ABS_X, x);
move[2].value = litest_scale(d, ABS_Y, y);
move[3].value = litest_scale(d, ABS_X, x);
move[4].value = litest_scale(d, ABS_Y, y);
ARRAY_FOR_EACH(move, ev)
litest_event(d, ev->type, ev->code, ev->value);
}
static struct litest_device_interface interface = {
.touch_down = litest_synaptics_clickpad_touch_down,
.touch_move = litest_synaptics_clickpad_move,
};
void
litest_create_synaptics_clickpad(struct litest_device *d)
{
struct input_absinfo abs[] = {
{ ABS_X, 1472, 5472, 75 },
{ ABS_Y, 1408, 4448, 129 },
{ ABS_PRESSURE, 0, 255, 0 },
{ ABS_TOOL_WIDTH, 0, 15, 0 },
{ ABS_MT_SLOT, 0, 1, 0 },
{ ABS_MT_POSITION_X, 1472, 5472, 75 },
{ ABS_MT_POSITION_Y, 1408, 4448, 129 },
{ ABS_MT_TRACKING_ID, 0, 65535, 0 },
test: add litest helper functions for creating uinput devices Both functions accept a series of event types/codes tuples, terminated by -1. For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used as a property to enable. The _abs function als takes an array of absinfo, with absinfo.value determining the axis to change. If none are given, abs axes are initialized with default settings. Both functions abort on failure, so the caller does not need to check the return value. Example code for creating a rel device: struct libevdev_uinput *uinput; struct input_id id = { ... }; uinput = litest_create_uinput_device("foo", &id, EV_REL, REL_X, EV_REL, REL_Y, EV_KEY, BTN_LEFT, INPUT_PROP_MAX, INPUT_PROP_BUTTONPAD, -1); libevdev_uinput_write_event(uinput, EV_REL, REL_X, -1); libevdev_uinput_write_event(uinput, EV_SYN, SYN_REPORT, 0); ... libevdev_uinput_destroy(uinput); Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-26 20:09:42 +10:00
{ ABS_MT_PRESSURE, 0, 255, 0 },
{ .value = -1 },
};
struct input_id id = {
.bustype = 0x11,
.vendor = 0x2,
.product = 0x11,
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
};
d->interface = &interface;
test: add litest helper functions for creating uinput devices Both functions accept a series of event types/codes tuples, terminated by -1. For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used as a property to enable. The _abs function als takes an array of absinfo, with absinfo.value determining the axis to change. If none are given, abs axes are initialized with default settings. Both functions abort on failure, so the caller does not need to check the return value. Example code for creating a rel device: struct libevdev_uinput *uinput; struct input_id id = { ... }; uinput = litest_create_uinput_device("foo", &id, EV_REL, REL_X, EV_REL, REL_Y, EV_KEY, BTN_LEFT, INPUT_PROP_MAX, INPUT_PROP_BUTTONPAD, -1); libevdev_uinput_write_event(uinput, EV_REL, REL_X, -1); libevdev_uinput_write_event(uinput, EV_SYN, SYN_REPORT, 0); ... libevdev_uinput_destroy(uinput); Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-26 20:09:42 +10:00
d->uinput = litest_create_uinput_abs_device("SynPS/2 Synaptics TouchPad", &id,
abs,
EV_KEY, BTN_LEFT,
EV_KEY, BTN_TOOL_FINGER,
EV_KEY, BTN_TOOL_QUINTTAP,
EV_KEY, BTN_TOUCH,
EV_KEY, BTN_TOOL_DOUBLETAP,
EV_KEY, BTN_TOOL_TRIPLETAP,
EV_KEY, BTN_TOOL_QUADTAP,
-1, -1);
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
}
struct litest_test_device litest_synaptics_clickpad_device = {
.type = LITEST_SYNAPTICS_CLICKPAD,
.features = LITEST_TOUCHPAD | LITEST_CLICKPAD | LITEST_BUTTON,
.shortname = "synaptics",
.setup = litest_synaptics_clickpad_setup,
.teardown = litest_generic_device_teardown,
.create = litest_create_synaptics_clickpad,
};
Reference in a new issue Copy permalink