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

110 lines
3.8 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);
}
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
static struct input_event down[] = {
{ .type = EV_KEY, .code = BTN_TOOL_FINGER, .value = 1 },
{ .type = EV_KEY, .code = BTN_TOUCH, .value = 1 },
{ .type = EV_ABS, .code = ABS_X, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_Y, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_PRESSURE, .value = 30 },
{ .type = EV_ABS, .code = ABS_MT_SLOT, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_MT_TRACKING_ID, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_MT_POSITION_X, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_MT_POSITION_Y, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_SYN, .code = SYN_REPORT, .value = 0 },
{ .type = -1, .code = -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
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
static struct input_event move[] = {
{ .type = EV_ABS, .code = ABS_MT_SLOT, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_X, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_Y, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_MT_POSITION_X, .value = LITEST_AUTO_ASSIGN },
{ .type = EV_ABS, .code = ABS_MT_POSITION_Y, .value = LITEST_AUTO_ASSIGN },
{ .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 },
{ .type = -1, .code = -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
static struct litest_device_interface interface = {
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
.touch_down_events = down,
.touch_move_events = move,
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
};
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
static struct input_id input_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
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
static int events[] = {
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,
};
static struct input_absinfo absinfo[] = {
{ 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 },
{ ABS_MT_PRESSURE, 0, 255, 0 },
{ .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
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,
test: allow for description-based test devices Most of the test devices now are static descriptions anyway, make them fully static now, including for touch events. Switch the synaptics device now as example, the rest comes later for easier patch review. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 10:00:16 +10:00
.interface = &interface,
.name = "SynPS/2 Synaptics TouchPad",
.id = &input_id,
.events = events,
.absinfo = absinfo,
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
};
Reference in a new issue Copy permalink