Lines Matching refs:input

1 Programming input drivers
4 1. Creating an input device driver
10 Here comes a very simple example of an input device driver. The device has
14 #include <linux/input.h>
76 First it has to include the <linux/input.h> file, which interfaces to the
77 input subsystem. This provides all the definitions needed.
83 Then it allocates a new input device structure with input_allocate_device()
84 and sets up input bitfields. This way the device driver tells the other
85 parts of the input systems what it is - what events can be generated or
86 accepted by this input device. Our example device can only generate EV_KEY
96 Then the example driver registers the input device structure by calling
100 This adds the button_dev structure to linked lists of the input driver and
101 calls device handler modules _connect functions to tell them a new input
114 call to the input system. There is no need to check whether the interrupt
116 the input system, because the input_report_* functions check that
161 Note that input core keeps track of number of users for the device and
173 It's reported to the input system via:
177 See linux/input.h for the allowable values of code (from 0 to KEY_MAX).
179 pressed, zero value means key released. The input code generates events only
234 The dev->name should be set before registering the input device by the input
239 of the device. The bus IDs are defined in input.h. The vendor and device ids
241 should be set by the input device driver before registering it.
243 The idtype field can be used for specific information for the input device
251 These three fields should be used by input devices that have dense keymaps.
252 The keycode is an array used to map from scancodes to input system keycodes.
265 keycode/keycodesize/keycodemax mapping mechanism provided by input core
271 ... is simple. It is handled by the input.c module. Hardware autorepeat is
275 handled by the input system.
286 direction - from the system to the input device driver. If your input device