Lines Matching refs:t

33 		    printk(KERN_ERR "button.c: Can't allocate irq %d\n", button_irq);
113 routine isn't reporting two same value events (press, press for example) to
122 This doesn't seem important in the one button case, but is quite important
123 for example for mouse movement, where you don't want the X and Y values
129 In case the driver has to repeatedly poll the device, because it doesn't
139 		    printk(KERN_ERR "button.c: Can't allocate irq %d\n", button_irq);
198 doesn't mean that it should be impossible be wake the system up on LAN through
204 inhibiting one interface shouldn't affect the device's capability of being a
230 because it doesn't have any absolute coordinate system to work in. Absolute
261 If you don't need absfuzz and absflat, you can set them to zero, which mean
348 isn't a rule), and thus must not sleep, and must not take too long to finish.