Searched refs:evdev (Results 1 – 13 of 13) sorted by relevance
38 struct evdev { struct57 struct evdev *evdev; argument215 struct evdev *evdev = client->evdev; in evdev_pass_values() local240 wake_up_interruptible(&evdev->wait); in evdev_pass_values()249 struct evdev *evdev = handle->private; in evdev_events() local260 client = rcu_dereference(evdev->grab); in evdev_events()265 list_for_each_entry_rcu(client, &evdev->client_list, node) in evdev_events()292 struct evdev *evdev = client->evdev; in evdev_flush() local294 mutex_lock(&evdev->mutex); in evdev_flush()296 if (evdev->exist && !client->revoked) in evdev_flush()[all …]
17 obj-$(CONFIG_INPUT_EVDEV) += evdev.o
149 module will be called evdev.
44 struct clock_event_device *evdev = dev_id; in timer_interrupt() local55 evdev->event_handler(evdev); in timer_interrupt()67 struct clock_event_device *evdev) in comparator_next_event() argument84 struct clock_event_device *evdev) in comparator_mode() argument88 pr_debug("%s: start\n", evdev->name); in comparator_mode()100 pr_debug("%s: stop\n", evdev->name); in comparator_mode()101 if (evdev->mode == CLOCK_EVT_MODE_ONESHOT || in comparator_mode()102 evdev->mode == CLOCK_EVT_MODE_RESUME) { in comparator_mode()
33 struct clock_event_device *evdev = dev_id; in timer_interrupt() local37 evdev->event_handler(evdev); in timer_interrupt()49 struct clock_event_device *evdev) in score_timer_set_next_event() argument59 struct clock_event_device *evdev) in score_timer_set_mode() argument
180 struct clock_event_device *evdev = dev_id; in nmdk_timer_interrupt() local183 evdev->event_handler(evdev); in nmdk_timer_interrupt()
52 Perhaps at some point an abstract function will be placed into evdev so
22 1. have your kernel configured with evdev and a driver that supports your24 2. make sure evdev module is loaded and /dev/input/event* device files are
178 for example evdev225 3.2.4 evdev227 evdev is the generic input event interface. It passes the events
73 sent in the evdev event stream.89 - Used to indicate buffer overrun in the evdev client's event queue.125 BTN_TOUCH must be the first evdev code emitted in a synchronization frame.
246 The id and name fields can be passed to userland via the evdev interface.257 EVIOCGKEYCODE and EVIOCSKEYCODE ioctls on corresponding evdev interface.
417 For example, use the xf86-input-evdev driver for an X pointing device.
336 The events will show up as scancodes F1 through F9 via evdev.