Lines Matching refs:and

11 just one button and the button is accessible at i/o port BUTTON_PORT. When
84 and sets up input bitfields. This way the device driver tells the other
87 type events, and from those only BTN_0 event code. Thus we only set these
100 This adds the button_dev structure to linked lists of the input driver and
102 device has appeared. input_register_device() may sleep and therefore must
109 which upon every interrupt from the button checks its state and reports it
125 for for example mouse movement, where you don't want the X and Y values
128 1.2 dev->open() and dev->close()
132 have an interrupt coming from it and the polling is too expensive to be done
134 can use the open and close callback to know when it can stop polling or
135 release the interrupt and when it must resume polling or grab the interrupt
161 Note that input core keeps track of number of users for the device and
163 to the device and that dev->close() is called when the very last user
172 The most simple event type is EV_KEY, which is used for keys and buttons.
182 In addition to EV_KEY, there are two more basic event types: EV_REL and
183 EV_ABS. They are used for relative and absolute values supplied by the
187 events are namely for joysticks and digitizers - devices that do work in an
191 set the corresponding bits and call the
213 it sometimes reports more, but it must be able to always reach the min and
214 max values), with noise in the data up to +- 4, and with a center flat
217 If you don't need absfuzz and absflat, you can set them to zero, which mean
218 that the thing is precise and always returns to exactly the center position
231 1.5 The id* and name fields
238 The id* fields contain the bus ID (PCI, USB, ...), vendor ID and device ID
239 of the device. The bus IDs are defined in input.h. The vendor and device ids
240 are defined in pci_ids.h, usb_ids.h and similar include files. These fields
246 The id and name fields can be passed to userland via the evdev interface.
253 The keycode max should contain the size of the array and keycodesize the
256 Userspace can query and alter current scancode to keycode mappings using
257 EVIOCGKEYCODE and EVIOCSKEYCODE ioctls on corresponding evdev interface.
259 rely on kernel's default implementation of setting and querying keycode
262 1.7 dev->getkeycode() and dev->setkeycode()
264 getkeycode() and setkeycode() callbacks allow drivers to override default
266 and implement sparse keycode maps.
272 not used, because it's not present in many devices and even where it is
288 *and* also the callback routine:
302 isn't a rule), and thus must not sleep, and must not take too long to finish.