Commit 4c4d400b authored by Peter Hutterer's avatar Peter Hutterer

test: fix the 'all codes' keyboard device

The ...create() method returned the wrong device, so this one was never
actually used. Once we start using, we get test case failures related to the
device having BTN_foo events as well. For now, just disable those codes so we
have a keyboard with all keys and pass the tests. The rest needs better
fixing.
Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
parent a6f0e4ae
......@@ -30,7 +30,7 @@ static void all_codes_create(struct litest_device *d);
static void litest_keyboard_all_codes_setup(void)
{
struct litest_device *d = litest_create_device(LITEST_KEYBOARD);
struct litest_device *d = litest_create_device(LITEST_KEYBOARD_ALL_CODES);
litest_set_current_device(d);
}
......@@ -61,6 +61,11 @@ all_codes_create(struct litest_device *d)
int code, idx;
for (idx = 0, code = 0; code < KEY_MAX; code++) {
const char *name = libevdev_event_code_get_name(EV_KEY, code);
if (name && strneq(name, "BTN_", 4))
continue;
events[idx++] = EV_KEY;
events[idx++] = code;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment