Searched full:buttons (Results 1 – 25 of 46) sorted by relevance
12
| /Documentation/input/ |
| D | gamepad.rst | 44 4 buttons in diamonds-shape (on the right side). The buttons are 48 4 buttons (on the left side) that point up, down, left and right. 50 Different constellations, but most-times 2 buttons: SELECT - START 52 special system-button. It often looks different to the other buttons and 60 Not all devices provide them, but the upper buttons are normally named 61 Left- and Right-Triggers, the lower buttons Z-Left and Z-Right. 83 the buttons from this protocol. However, they try to do this in a compatible 84 fashion. For example, the "Nintendo Wii Nunchuk" provides two trigger buttons 86 analog stick and two trigger buttons on the right side. 101 Every gamepad device has at least 2 action buttons. This means, that every [all …]
|
| D | gameport-programming.rst | 75 int my_cooked_read(struct gameport *gameport, int *axes, int *buttons) 81 buttons[0] = my_mmio[4]; 175 Read the buttons and ns558 oneshot bits. If set to NULL, inb(io) will be 180 int (*cooked_read)(struct gameport *, int *axes, int *buttons); 184 and buttons[0] with four bits representing the buttons.
|
| D | event-codes.rst | 41 - Used to describe state changes of keyboards, buttons, or other key-like 383 device but do not have physical buttons associated with the trackstick 385 visual/haptic areas for left, middle, right buttons intended to be used 388 If INPUT_PROP_TOPBUTTONPAD is set, userspace should emulate buttons 415 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report 447 BTN_{STYLUS,STYLUS2} should be used to report buttons on the tool itself. Any 448 button may be used for buttons on the tablet except BTN_{MOUSE,LEFT}. 449 BTN_{0,1,2,etc} are good generic codes for unlabeled buttons. Do not use 450 meaningful buttons, like BTN_FORWARD, unless the button is labeled for that
|
| /Documentation/input/devices/ |
| D | xpad.rst | 10 Due to backwards compatibility all buttons are reported as digital. 12 have only digital face buttons. 23 The number of buttons/axes reported varies based on 3 things: 28 module configuration for "Map D-PAD to buttons rather than axes for unknown 33 If you said Y it will map the d-pad to buttons, which is needed for dance 47 axes and 10 buttons. 54 All of the 10 buttons work (in digital mode). The six buttons on the 66 When using a known dance pad, jstest will report 6 axes and 14 buttons. 73 Known dance pads automatically map the d-pad to buttons and will work 77 of buttons, see section 0.3 - Unknown Controllers [all …]
|
| D | alps.rst | 33 00-00-64 if no buttons are pressed. The bits 0-2 of the first byte will be 1s 34 if some buttons are pressed. 87 extra buttons, stick buttons on a dualpoint, etc. 102 pointingstick and touchpad buttons. 130 the pointingstick and touchpad buttons, except for Dell dualpoint devices 131 where the pointingstick buttons get reported separately in the PSM, PSR 170 Note that for some devices the trackstick buttons are reported in this packet, 200 processing is enabled. SW means scroll up when 4 buttons are available.
|
| D | atarikbd.rst | 63 The mouse buttons can be treated as part of the mouse or as additional 90 MOUSE BUTTON ACTION has set the buttons to act like part of the keyboard. 112 break code for the appropriate cursor key. The mouse buttons produce scan 173 for the appropriate cursor motion keys. The trigger or fire buttons of the 203 reporting mode for joystick 1, with both buttons being logically assigned to 207 both buttons are logically connected to it. If a mouse disable command is 252 ; mss=100, mouse buttons act like keys 254 This command sets how the ikbd should treat the buttons on the mouse. The 255 default mouse button action mode is %00000000, the buttons are treated as part 257 When buttons act like keys, LEFT=0x74 & RIGHT=0x75. [all …]
|
| D | joystick-parport.rst | 115 connectors. Anyway, if you've got a gamepad, and it has buttons A, B, Turbo 118 also use 5 wires, but have more buttons. They will work as well, of course:: 263 For joysticks with two buttons you connect the second button to pin 7 on 280 including 1 and 2 buttons Multisystem joysticks. 322 Steffen's version, there is support for up to 5 buttons per joystick. However, 388 to the Sega Master System pads. They use more buttons (3+1, 5+1, 6+1). Use 416 Sega Saturn has eight buttons, and to transfer that, without hacks like 555 3 Genesis pad (3+1 buttons) 556 5 Genesis pad (5+1 buttons) 557 6 Genesis pad (6+2 buttons) [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | google,cros-ec-keyb.yaml | 19 switches/buttons like power and volume buttons. 24 - description: ChromeOS EC with only buttons/switches 26 - description: ChromeOS EC with keyboard and possibly buttons/switches 136 /* No matrix keyboard, just buttons/switches */
|
| D | adc-keys.yaml | 7 title: ADC attached resistor ladder buttons 23 const: buttons 82 io-channel-names = "buttons";
|
| D | ibm,op-panel.yaml | 17 server. It has a display and three buttons: two directional arrows and one
|
| D | adafruit,seesaw-gamepad.yaml | 26 X, A, B, Y -> Digital action buttons
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-kovaplus | 66 press of a button. A profile is split in settings and buttons. 69 buttons back to the mouse. The data has to be 23 bytes long. 81 press of a button. A profile is split in settings and buttons. 83 When read, these files return the respective profile buttons. 93 press of a button. A profile is split in settings and buttons. 109 press of a button. A profile is split in settings and buttons.
|
| D | sysfs-driver-hid-roccat-pyra | 55 press of a button. A profile is split in settings and buttons. 58 buttons back to the mouse. The data has to be 19 bytes long. 70 press of a button. A profile is split in settings and buttons. 72 When read, these files return the respective profile buttons. 82 press of a button. A profile is split in settings and buttons. 98 press of a button. A profile is split in settings and buttons.
|
| D | sysfs-driver-hid-roccat-koneplus | 59 press of a button. A profile is split in settings and buttons. 62 buttons back to the mouse. The data has to be 77 bytes long. 74 press of a button. A profile is split in settings and buttons. 76 When read, these files return the respective profile buttons. 86 press of a button. A profile is split in settings and buttons. 102 press of a button. A profile is split in settings and buttons.
|
| D | sysfs-driver-hid-roccat-savu | 1 …config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons 6 button settings. The buttons variable holds information about 8 respective profile buttons to the mouse. The data has to be
|
| D | sysfs-driver-hid-roccat-arvo | 39 When read, this file returns the current state of the buttons. 40 When written, the given buttons are activated/deactivated
|
| D | sysfs-driver-hid-roccat-konepure | 44 press of a button. A profile is split in settings and buttons. 47 buttons back to the mouse. The data has to be 59 bytes long. 59 press of a button. A profile is split in settings and buttons.
|
| /Documentation/devicetree/bindings/sound/ |
| D | nuvoton,nau8824.yaml | 75 Number of buttons supported. 83 Impedance threshold for each button. Array that contains up to 8 buttons 181 // Setup 4 buttons impedance according to Android specification
|
| D | nuvoton,nau8825.yaml | 81 Number of buttons supported. 89 Impedance threshold for each button. Array that contains up to 8 buttons 224 // Setup 4 buttons impedance according to Android specification
|
| D | dialog,da7219.yaml | 146 Impedance threshold between buttons A and D. 153 Impedance threshold between buttons D and B. 160 Impedance threshold between buttons B and C.
|
| D | qcom,wcd934x.yaml | 100 qcom,mbhc-buttons-vthreshold-microvolt: 222 … qcom,mbhc-buttons-vthreshold-microvolt = <75000 150000 237000 500000 500000 500000 500000 500000>;
|
| /Documentation/input/joydev/ |
| D | joystick-api.rst | 26 to 2 axes, and applications using it usually decode only 2 buttons, although 232 #define JSIOCGBUTTONS /* get number of buttons char */ 314 int buttons; /* immediate button state */ 323 To test the state of the buttons, 327 first_button_state = js.buttons & 1; 328 second_button_state = js.buttons & 2;
|
| D | joystick.rst | 100 move the stick, and press its buttons. The axes should all be zero when the 149 It also supports extensions like additional hats and buttons compatible 161 For other joystick types (more/less axes, hats, and buttons) support 182 fullchf CH Flightstick compatible with two hats and 6 buttons 203 8 CHF Buttons X and Y 211 16 Saitek F1-F4 Buttons 241 There is one caveat with the 3D Pro. There are 9 buttons reported, 503 models; the additional buttons on the 'Plus' versions are not supported yet.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | iqs62x.yaml | 56 * Dual capacitive buttons with proximity-activated function, unipolar lid 142 /* Dual capacitive buttons with volume knob. */
|
| /Documentation/arch/x86/ |
| D | usb-legacy-support.rst | 20 features (wheel, extra buttons, touchpad mode) of the real PS/2 mouse may
|
12