Drivers NXP Input Devices

  
Drivers Catalog ⇒ Human Interface Devices ⇒ Full List of Human Interface Devices

Input Devices - Tools for inserting all types of information into the computer. They make up the hardware interface between the operation system and device, which is often connected via USB cable. Depending on the type of data input, all instruments are divided into 4 types: demonstrative, graphics, sound and game.
By pointing input devices are included followings: keyboard, mouse, trackball, touchpad, joystick and light pen. All they send certain signals, whereby the computer performs the specified actions. Drivers for USB input devices recognize the signals for the system. This category also includes a touch screen, which is used to communicate with the PC and uses the touch of your fingers.
By the method of the cursor control tools are divided into direct, engaged directly in the input cursor visibility, and indirect, by entering the no cursor visibility.
By graphical input devices are included followings: video capture card, scanner, web camera and digital camera. The microphone and digital recorders are used to insert the audio information to the row. Different type of input devices are considered to be installed: the gaming peripherals, joysticks, levers motion simulators, gamepads, steering wheels, pedals and dance platforms.
All of the above tools are typically connected to the PC / laptop via the high speed interface USB. For their stable performance and fine-tuning it is recommended to download drivers for USB input devices.

Here are manufacturers of Human Interface Devices, drivers for which you can download on our website. 4833 drivers for 672 devices from 59 manufacturers, you can download absolutely free of charge. Select the desired device, the manufacturer or the device ID.

NXP Semiconductors. The MCUXpresso SDK provides a peripheral driver for the General-Purpose Input/Output (GPIO) module of MCUXpresso SDK devices. For devices of type GUIDCLASSMOUSE, a device's function driver: Handles device-specific input. Creates the MOUSEINPUTDATA structures required by MouseClassServiceCallback. Transfers MOUSEINPUTDATA structures to the Mouclass data queue by calling MouseClassServiceCallback in its ISR dispatch completion routine.

  1. A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows.
  2. Remnant USB device drivers can remain and interfere with the installation of Dictaphone input devices such as GoMD, PowerMic, USB footpedal, and the Olympus and Grundig portables. This article provides a troubleshooting procedure to eliminate drivers for non-present devices on client workstations.
  3. Input drivers can also emit motion events to connect a pointing device to the framework, such as a touchpad or mouse. These devices report an absolute position value as an x/y coordinate. Each event includes an optional pressed state to indicate if the event represents a 'tap' or 'click' event at that location.

Top Vendors of Human Interface Devices

Top Models of Human Interface Devices

#VendorDevice Name
1 Cirque GlidePoint 3.3 USB Smart Cat (DS5)
2 Wacom Wacom Penabled Dual Touch
3 IVT Bluetooth HID Mouse
4 Microsoft Logitech USB Cordless Mouse
5 Cirque GlidePoint 3.6 PS/2 Easy Cat (Saturn)
6 Synaptics Synaptics USB Human Interface Device
7 Microsoft Genius USB Wheel Mouse
8 Dell Premium Tilt Wheel (HID)
9 Cirque GlidePoint 3.6 PS/2 Smooth Cat (DS4)
10 Microsoft Dispositivo de infrarrojos HID
11 Cirque GlidePoint 3.6 USB Smooth Cat (DS5)
12 Cirque GlidePoint 3.3 USB Smooth Cat (DS5)
13 Generic Virtual Hid Device
14 Cirque GlidePoint 3.3 USB Easy Cat (DS4)
15 Wacom Wacom capacitive touch
16 Logitech USB Optical MouseMan Wheel
17 Cirque GlidePoint 3.6 PS/2 Easy Cat (Pinnacle)
18 Logitech Logitech USB LS1 Laser Mouse
19 ITE ITECIR Infrared Receiver (SIO2)
20 Microsoft Logitech MouseMan Wheel (USB)
-->

The driver for the Xbox Common Controller class (XUSB) on Windows implements the kernel-mode interface for the XINPUT DLL. To provide a good experience for legacy titles that use the DirectInput API with the common controller device, the driver also exports a Human Interface Device (HID) class interface, which is picked up by DirectInput. We chose the mapping of XUSB to HID based on typical behavior in a set of gaming applications for the original XINPUT version, and we updated the mapping for newer subtypes. This topic describes the mapping.

Human Interface Device (HID)

HID standard is a standard from the Universal Serial Bus (USB) committee originally proposed by Microsoft to generalize protocols for input devices. It consists of a byte-code description language and can express gamepads, mice, joysticks, throttle and rudder controls, and multi-axis controllers. Because this standard is so generalized, you might have difficulty writing software that consumes input from arbitrary devices. Therefore, for the game-centric DirectInput API, we developed a specific sub-mapping of types to encourage hardware manufactures to support through their drivers.

Important

You can also access HID input devices via RawInput API and process input reports via low level HID API but vibration feedback will not work as with DirectInput.

Mappings

The XUSB driver implements both an XUSB class interface and a HID class interface for devices in order to support both XINPUT and DirectInput usage. This mapping is based on the XUSB subtype information. The driver implements four distinct groups of mappings.

XUSB SubtypeMapping
XINPUT_DEVSUBTYPE_GAMEPAD (Subtype 1)Gamepad
XINPUT_DEVSUBTYPE_WHEEL (Subtype 2)Wheel
XINPUT_DEVSUBTYPE_ARCADE_STICK (Subtype 3)Arcade Stick/Arcade Pad
XINPUT_DEVSUBTYPE_FLIGHT_STICK (Subtype 4)Flight Stick
XINPUT_DEVSUBTYPE_DANCE_PAD (Subtype 5)Default for any new subtype
XINPUT_DEVSUBTYPE_GUITAR (Subtype 6)Guitar
XINPUT_DEVSUBTYPE_GUITAR_ALTERNATE (Subtype 7)
XINPUT_DEVSUBTYPE_DRUM_KIT (Subtype 8)
XINPUT_DEVSUBTYPE_GUITAR_BASS (Subtype 11)
XINPUT_DEVSUBTYPE_ARCADE_PAD (Subtype 19)

Note

The following HID mappings are static. This means that even if the device capabilities report indicates that a particular button or axis is not supported, the mapping will still include it but will always report an off state or center value.

Gamepad

This is the default mapping and is designed around the standard Xbox Common Controller gamepad, and is exposed as a Gamepad HID usage type.

ControlHID Usage NameUsage PageUsage ID
Left StickX, Y0x010x30, 0x31
Right StickRx, Ry0x010x33, 0x34
Left Trigger + Right TriggerZ*0x010x32
D-Pad Up, Down, Left, RightHat Switch0x010x39
AButton 10x090x01
BButton 20x090x02
XButton 30x090x03
YButton 40x090x04
LB (left bumper)Button 50x090x05
RB (right bumper)Button 60x090x06
BACKButton 70x090x07
STARTButton 80x090x08
LSB (left stick button)Button 90x090x09
RSB (right stick button)Button 100x090x0A

Drivers Nxp Input Devices Bluetooth

Note

Input

(*): This is combined so that Z exhibits the centering behavior expected by most titles for rotation; this does mean it is not possible to see all possible trigger combination values through DirectInput and HID.

Arcade Stick/Arcade Pad

This is the mapping designed around the Arcade Stick controller, and is exposed as a Gamepad HID usage type. The Arcade Pad is very much like an Arcade Stick, but in a smaller form-factor. These designs replace the analog Left Trigger and Right Trigger with digital buttons that report the minimum and maximum axis value.

NXP
ControlHID Usage NameUsage PageUsage ID
D-Pad Up, Down, Left, RightHat Switch0x010x39
AButton 10x090x01
BButton 20x090x02
XButton 30x090x03
YButton 40x090x04
LB (left bumper)Button 50x090x05
RB (right bumper)Button 60x090x06
BACKButton 70x090x07
STARTButton 80x090x08
Left TriggerButton 90x090x09
Right TriggerButton 100x090x0A

Drivers Nxp Input Devices Device

These devices may or may not support additional controls, but these are not exposed by the HID mapping: Left Stick, Right Stick, LSB (left stick button), and RSB (right stick button).

Wheel

This mapping is designed around the Xbox Racing Wheel, and is exposed as a Gamepad HID usage type.

ControlHID Usage NameUsage PageUsage ID
Wheel (Left Stick X)X0x010x30
Accelerator Pedal (Right Trigger) + Brake Pedal (Left Trigger)Z*0x010x32
D-Pad Up, Down, Left, RightHat Switch0x010x39
AButton 10x090x01
BButton 20x090x02
XButton 30x090x03
YButton 40x090x04
LB (left bumper)Button 50x090x05
RB (right bumper)Button 60x090x06
LSB (left stick button)Button 70x090x07
RSB (right stick button)Button 80x090x08
BACKButton 90x090x09
STARTButton 100x090x0A

Note

(*): This is combined so that Z exhibits the centering behavior expected by most titles for the brake and accelerator controls; this does mean it is not possible to see all possible pedal combination values through DirectInput.

Flight Stick

Drivers NXP Input Devices

This mapping is designed around the Xbox Flight Stick, and is exposed as a Joystick HID usage type.

ControlUsage NameUsage PageUsage ID
Flight Stick (Left Stick)X, Y0x010x30, 0x31
POV Hat (Right Stick)Rx, Ry0x010x33, 0x34
Throttle (Right Trigger)Z0x010x32
Rudder (Left Trigger)Rz0x010x35
D-Pad Up, Down, Left, RightHat Switch0x010x39
Primary Weapon (A)Button 10x090x01
Secondary Weapon (B)Button 20x090x02
XButton 30x090x03
YButton 40x090x04
LB (left bumper)Button 50x090x05
RB (right bumper)Button 60x090x06
BACKButton 70x090x07
STARTButton 80x090x08
LSB (left stick button)Button 90x090x09
RSB (right stick button)Button 100x090x0A

Note

This is based on the final Flight Stick design. Because this differs from early Flight Stick definitions, many devices have a mode switch that supports the old versus new model. This mapping assumes the new model.