Searched refs:evdev (Results 1 – 17 of 17) sorted by relevance
28 struct evdev { struct47 struct evdev *evdev; argument145 ktime_t *ev_time = input_get_timestamp(client->evdev->handle.dev); in __evdev_queue_syn_dropped()294 struct evdev *evdev = handle->private; in evdev_events() local300 client = rcu_dereference(evdev->grab); in evdev_events()305 list_for_each_entry_rcu(client, &evdev->client_list, node) in evdev_events()331 struct evdev *evdev = container_of(dev, struct evdev, dev); in evdev_free() local333 input_put_device(evdev->handle.dev); in evdev_free()334 kfree(evdev); in evdev_free()341 static int evdev_grab(struct evdev *evdev, struct evdev_client *client) in evdev_grab() argument[all …]
20 obj-$(CONFIG_INPUT_EVDEV) += evdev.o
153 module will be called evdev.
94 struct clock_event_device *evdev = this_cpu_ptr(&riscv_clock_event); in riscv_timer_interrupt() local97 evdev->event_handler(evdev); in riscv_timer_interrupt()
177 struct clock_event_device *evdev = dev_id; in nmdk_timer_interrupt() local180 evdev->event_handler(evdev); in nmdk_timer_interrupt()
139 struct clock_event_device *evdev = this_cpu_ptr(&clint_clock_event); in clint_timer_interrupt() local142 evdev->event_handler(evdev); in clint_timer_interrupt()
14 A Remote Controller interface is mapped as a normal evdev/input
84 evdev subsection87 ``evdev`` is the generic input event interface. It passes the events107 evdev nodes are created with minors starting with 256.
27 1. have your kernel configured with evdev and a driver that supports your29 2. make sure evdev module is loaded and /dev/input/event* device files are
95 sent in the evdev event stream.115 - Used to indicate buffer overrun in the evdev client's event queue.158 BTN_TOUCH must be the first evdev code emitted in a synchronization frame.
27 libevdev is a wrapper library for evdev devices that provides interfaces to
290 The id and name fields can be passed to userland via the evdev interface.301 EVIOCGKEYCODE and EVIOCSKEYCODE ioctls on corresponding evdev interface.
61 Perhaps at some point an abstract function will be placed into evdev so
16 remote controller core is implemented on the top of the linux input/evdev
14 encouraged to switch to the generic event (``evdev``) interface.
455 For example, use the xf86-input-evdev driver for an X pointing device.
351 The events will show up as scancodes F1 through F9 via evdev.